Define and manage policy set bindings
Policy set bindings contain platform specific information, like keystore, authentication information or persistent information, required by a policy set attachment. Create and manage bindings.
In v7.0 and later, there are two types of bindings, application specific bindings and general bindings.
- Application specific bindings
Create application specific bindings only at a policy set attachment point. These bindings are specific to and constrained to the characteristics of the defined policy. Application specific bindings are capable of providing configuration for advanced policy requirements, such as multiple signatures; however, these bindings are only reusable within an application. Furthermore, application specific bindings have very limited reuse across policy sets.
When we create an application specific binding for a policy set attachment, the binding begins in a completely unconfigured state. We must add each policy, such as WS-Security or HTTP transport, to override the default binding and fully configure the bindings for each policy that we have added. For WS-Security policy, some high level configuration attributes such as TokenConsumer, TokenGenerator, SigningInfo, or EncryptionInfo might be obtained from the default bindings if they are not configured in the application specific bindings.
For service providers, we can only create application specific bindings by selecting...
-
Assign Binding > New Application Specific Binding for service provider resources that have an attached policy set
Similarly, for service clients, we can only create application specific bindings by selecting...
-
Assign Binding > New Application Specific Binding for service client resources that have an attached policy set
- General bindings
General bindings were introduced in v7.0. These bindings can be configured to be used across a range of policy sets and can be reused across applications and for trust service attachments. Though general bindings are highly reusable, they are however not able to provide configuration for advanced policy requirements, such as multiple signatures. There are two types of general bindings:
- General provider policy set bindings
- General client policy set bindings
Create general policy set bindings by copying an existing binding or by creating a new one. For WS-Security bindings, copy an existing sample binding. Creating a new policy set binding from scratch for WS-Security can cause unexpected problems at run time.
To create general provider policy set bindings, in the administrative console, select...
-
Services > Policy sets > General provider policy set bindings > New or Copy
To create general client policy set bindings, select...
-
Services > Policy sets > General client policy set bindings > New or Copy
See Define and manage service client or provider bindings. General provider policy set bindings can also be used for trust service attachments.
After we make a copy of the provider or client sample bindings, customize only the settings of our new copy to suit your purposes. Do not remove anything from your binding copy, such as token generators, token consumers, sign parts, or encrypt parts. We can add things to your binding copy if needed, but deleting information can cause unanticipated errors at run time.
Important: The general bindings that are shipped with the product are provider and client sample bindings. These bindings are initially set as the cell default bindings. Do not use these bindings in their current state in a production environment. To use the sample bindings, modify them to meet our security needs in a production environment. Alternatively, create a copy of the bindings and then modify the copy. For example, change the key and keystore settings to ensure security, and modify other settings to match the environment. We must also configure the username and password for Username or LTPA token authentication. See the topic Configure the username and password for WS-Security Username or LTPA token authentication for more information.
Depending on the assigned security role when security is enabled, we 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.
View or work with policy sets bindings
- To view your current policy set and application specific bindings from the administrative console, click...
-
Services > Policy sets > Application policy sets > policy_set_name > Attached applications > application
Depending on the application that we select, we can manage the bindings attached to the following policy sets:
- Service provider policy sets and bindings
- Service client policy sets and bindings
To learn more about managing the bindings attached to policy sets, see the service provider or service client policy sets and bindings information.
Sort on the Attached policy set column on either of the policy sets and bindings pages to select the service resources with the same policy set attached. Likewise, sort on the Binding column to select the service resources that share the same custom binding to attach to a different policy set. If we sort on the Policy Set or the Binding column, the hierarchical relationship of the service resources in the first column is not accurate. We can sort again on the Application/Service/Endpoint/Operation column to restore the hierarchical relationship. The entries in the Application/Service/Endpoint/Operation column display in ascending order.
- To work with an existing bindings from the administrative console, click...
-
Services > Policy sets > Application policy sets >policy_set_name > Attached applications > application name > [ Service provider policy sets and bindings | Service client policy sets and bindings ] > binding name
If no applications appear when you click Attached applications, we do not have any applications attached to the selected policy set. To attach a policy set and binding to an application using the administrative console, click...
-
Applications > Enterprise Applications > application name > [Service provider policy sets and bindings | Server client policy sets and bindings
- [Optional] To work with general bindings, click...
-
Services > Policy sets > [General client policy set bindings | Services > Policy sets > General provider policy set bindings]
We can complete the following actions for general bindings:
- Import policy set bindings
- Export policy sets bindings settings
- Define and manage service client or provider bindings
- Create new or configuring existing general binding settings
- Copy policy set binding settings
- Delete policy set bindings
When we finish this task, we would have performed one or more of the following:
- Created an application specific or general policy set binding
- Imported a policy set binding
- Exported a policy set binding
- Deleted a policy set binding
- Modified an application attachment to apply an application specific binding for single security domain
- Modified an application attachment to apply an application specific binding for multiple security domain
Subtopics
- Web services policy set bindings
- Create application specific bindings for policy set attachment
- Setting server default bindings for policy sets
- Setting default policy set bindings
- Modify default bindings at the server or cell level for policy sets
- Reassigning bindings to policy sets attachments
- Policy set bindings settings
- Web Services Addressing policy set binding