WAS v8.5 > Reference > Sets

References policy sets and bindings collection for SCA composites

Use this page to attach and detach policy sets to a composition unit, a service reference, its endpoints, or operations of a Service Component Architecture (SCA) composite. We can select the default bindings, create new application-specific bindings, or use bindings created for an attached policy set. We can view or change whether the service reference can share its current policy configuration.

To view this dmgr console page, your composition unit must use web services and support SCA. Click Applications > Application Types > Business-level applications > application_name > deployed_asset_composition_unit_name > References policy sets and bindings.

Depending on your assigned security role when security is enabled, you might not have access to text entry fields or buttons to create or edit configuration data. Review the administrative roles documentation to learn more about the valid roles for the application server.

To attach or detach a policy set or binding, do the following:

  1. Select a composition unit, service, endpoint, or operation. The Composition unit/Service/Endpoint/Operation list is nested, indicating parent-child relationships.

  2. Click the desired button.

Button descriptions. Use the buttons to attach or detach client policy sets and to assign policy set bindings.

Button Resulting action
Attach Client Policy Set Attaches a client policy set to the selected composition unit, service, endpoint, or operation. To attach a policy set, select a composition unit, service, endpoint, or operation and click Attach Client Policy Set > policy_set_option.

To close the menu list, click Attach Client Policy Set.

Detach Client Policy Set Detaches a client policy set from the selected composition unit, service, endpoint, or operation.

After the policy set is detached, if there is no policy set attached to an upper-level service resource, the Attached Client Policy Set column displays None and the Binding column displays Not applicable.

If there is a policy set attached to an upper-level service resource, the Attached Client Policy Set column displays policy_set_name (inherited) and the binding used for the upper-level attachment is applied. The binding name is displayed followed by (inherited).

Assign Binding Assigns a policy set binding to the selected composition unit, service, endpoint, or operation. The options include the following:

Default

Default binding for the selected service, endpoint, or operation. We can specify client and provider default bindings to be used at the cell level or global security domain level, for a particular server, or for a security domain. The default bindings are used when an application-specific binding has not been assigned to the attachment. When you attach a policy set to a service resource, the binding is initially set to the default. If we do not specifically assign a binding to the attachment point using this Assign Binding action, the default specified at the nearest scope is used.

For any policy set attachment, the run time checks to see if the attachment includes a binding. If so, it uses that binding. If not, the run time checks in the following order and uses the first available default binding:

  1. Default general bindings for the server
  2. Default general bindings for the domain in which the server resides
  3. Default general bindings for the global security domain

New Application Specific Binding

Select this option to create a new application-specific binding for the policy set attachments. The new binding you create is used for the selected resources. If you select more than one resource, ensure that all selected resources have the same policy set attached.

Client sample

Select this option to use the Client sample binding.

Client sample V2

Select this option to use the Client sample V2 binding when we are using either the Kerberos V5 WSSecurity default or the TrustServiceKerberosDefault policy sets.

Saml Bearer Client sample

Select this option to use the Saml Bearer Client sample. The Saml Bearer Client sample extends the Client sample binding to support SAML Bearer token usage scenarios. We can use this sample with any of the SAML bearer token default policy sets.

Saml HoK Symmetric Client sample

Select this option to use the Saml HoK Symmetric Client sample. The Saml HoK Symmetric Client sample extends the Client sample binding to support SAML holder-of-key (HoK) symmetric key token usage scenarios. We can use this sample with one of the SAML HoK Symmetric key default policy sets: either SAML11 HoK Symmetric WSSecurity default or SAML20 HoK Symmetric WSSecurity default.


Composition unit/Service/Endpoint/Operation

Name of the composition unit and the associated service references, endpoints or operations.

The Composition unit/Service/Endpoint/Operation column lists the service composition unit and the service references, endpoints, or operations the composition unit contains.


Attached Client Policy Set

Policy set that is attached to a composition unit, service reference, endpoint, or operation.

The Attached Client Policy Set column can contain the following values:

When the value in the column is a link, click the link to view or change settings about the attached policy set.


Binding

Binding configuration that is available for a service reference, endpoint, or operation.

The Binding column can contain the following values:

When the value in the Binding column is a link, click the link to view or change settings about the binding.


Related


Attach policy set settings
Create SCA business-level applications
Define and managing policy set bindings
Define and managing service client or provider bindings
Manage policy sets


+

Search Tips   |   Advanced Search