Define and manage service client or provider bindings
Service client or provider bindings are general bindings. We can create, copy, and manage general bindings such as the client or provider policy set bindings. These bindings provide system-specific configuration and can be reused across policy set attachments.
We cannot assign a binding to a service provider resource that does not have a policy set or has an inherited attachment. To assign a binding to such a service provider resource, first attach a policy set to the resource. Also, we cannot assign a binding to a service client resource that does not have an effective policy configuration or has an inherited policy attachment. To assign a binding to such a service client resource, first attach a policy set or specify the use of the provider policy. For more information, read about attaching a policy set to a service artifact.
There are two types of bindings, application specific bindings and general bindings.
Application specific binding
We can create application specific bindings only at a policy set attachment point. These bindings are specific to and defined by the characteristics of the 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 limited reuse across policy sets.
When creating an application specific binding for a policy set attachment, the binding begins in an 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 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 do not 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
Important: The general bindings that are included with the product are provider and client sample bindings. Do not use these bindings in their current state in a production environment. However, if they were modified to contain non-sample data, they could be used in a production environment.
Depending on the 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.
We can complete the following tasks to define and manage general client or provider policy set bindings.
- To create a new general client or provider policy set binding or to manage the binding configuration from the administrative console, click Services > Policy sets > General client policy set bindings > New. We can also access this panel by clicking Services > Policy sets > General provider policy set bindings > New. Use the resulting detail panel to create a new client or provider policy set binding. For more information, read about creating new or configuring existing general binding settings.
- To copy a specific policy set binding, select the binding name from the table and click Copy. For more information, read about copying a policy set binding settings.
- To import a client or provider policy set binding, click Import. Read about importing policy set bindings using the administrative console to complete the import task.
- To export a client or provider policy set binding, select the binding name from the table, and click Export. For more information, read about export policy set binding settings.
- To delete a policy set binding, select the binding name from the table, and click Delete. For more information, read about deleting policy set bindings.
Results
When you finish this task, we have created, copied, exported, imported or deleted a client or provider policy set binding.
Subtopics
- Service client or provider policy set bindings collection
Use this page to create, copy, and manage general policy set bindings, such as the service client or provider bindings. These bindings provide system-specific configuration, and can be reused across policy set attachments. We can select the general default bindings, create new general bindings, or use existing bindings for an attached policy set.
- Create new or configuring existing general binding settings
Use this page to create a new client or provider policy set binding. We can also use this page to configure an existing general binding. Empty bindings will be deleted. Scoping a binding to a security domain constrains the configuration options to those applicable to that domain and limits use of the binding to the specified domain.
Related tasks
Attaching a policy set to a service artifact Import policy set bindings using the administrative console
Export policy sets bindings settings Copy policy set binding settings Delete policy set bindings