WAS v8.5 > Secure applications > Secure web services > Define and managing secure policy set bindings

Configure the callers for general and default bindings

The caller specifies the token or message part used for authentication.

Before we can complete this task, create a new policy set and attach it to a service, or copy and edit one of the sample system policy sets. For more information, read the topics Creating policy sets using the dmgr console and Attaching a policy set to a service artifact.

The caller is used to indicate which of the tokens on the incoming message is the caller of the request. This information is used to create authentication credentials. We can use the dmgr console to access, configure caller settings for tokens and message parts. WAS v8.5 provides support for multiple callers. The caller token used for authentication is the one with highest priority, based on decreasing order of preference. We can modify the order of the callers, as described in the topic Changing the order of the callers for a token or message part.

1. Create a new policy set and attach it to a service, or copy and edit a sample system policy set. Add the WS-Security policy, as described in the topic Creating policy sets using the dmgr console.
2. Edit the general or default bindings for the WS-Security policy.
   • To edit general provider bindings for WebSphere Application Server version 7.0 and later, click Services > Policy Sets > General Provider policy set bindings. A caller is specified for the provider bindings only, not for the client bindings.
   • To edit default bindings for WAS v6.x, click Services > Policy Sets > Default policy set bindings.

3. cd Callers panel by clicking on the WS-Security policy, then click the Caller link.

4. Click New to create a new caller.

5. Enter the Name and Caller identity local part information for the new caller. For more information, read about caller settings.

6. When we have finished entering the configuration information for the caller, click Apply to save the caller.

7. If this is the first caller created for the policy set, the caller is automatically assigned as the highest priority caller, with an order of 1 (one). If other callers are already defined, the new caller is added at the end of the ordered list and is automatically assigned the lowest priority. We can change the order of the callers using the Move up and Move down buttons.

Results

When assigning orders to callers for migrated bindings, the callers are initially displayed with no order attribute. We cannot save the bindings until you assign order attributes to all the callers. Use the Move up and Move down buttons to change the order of the callers until they are in the correct order.

Related

Create policy sets
Attaching a policy set to a service artifact
Change the order of the callers for a token or message part

Reference:

Caller settings

+

Search Tips   |   Advanced Search