+

Search Tips   |   Advanced Search

Caller settings


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

Configure the caller settings for message parts when you are editing a default cell or server binding. We can also configure application specific bindings for tokens and message parts that are required by the policy set.

To view this admin console page when we are editing a general provider binding...

  1. Click Services > Policy sets > General provider policy sets bindings.

  2. Click the WS-Security policy in the Policies table.

  3. Click the Authentication and protection link in the Main message security policy bindings section.

  4. Click the Caller link in the Main message security policy bindings section.

  5. Click New.

To view this admin console page when we are configuring application specific bindings for tokens and message parts that are required by the policy set...

  1. Click Applications > Application Types > WebSphere enterprise apps .

  2. Select an application that contains Web services. The application must contain a service provider or a service client.

  3. Click the Service provider policy sets and bindings link in the Web Services Properties section. The caller settings are available only for the service provider policy sets and bindings. The caller settings are not available for service client.policy sets and bindings.

  4. Select a binding. You must have previously attached a policy set and assigned a application specific binding.

  5. Click the WS-Security policy in the Policies table.

  6. Click the Caller link in the Main message security policy bindings section.

  7. Click New.

    By creating a new caller it will automatically be assigned the next available order. We can change the order of preference, as described in the Order section below.

This admin console panel applies only to Java™ API for XML Web Services (JAX-WS) applications.

Name

Name of the caller to use for authentication. Enter a caller name in this required field. This arbitrary name identifies this caller setting.

Order

Order of preference for the callers. The order determines which caller will be utilized when multiple authentication tokens are received.

We can change the order of preference by moving a caller up or down in the list. Click the checkbox next to a caller name to select the caller, then click the Move up button to move the caller higher in the list, or click the Move down button to move the caller to a lower position in the preference order.

Button Resulting Action
Move up Moves the order of the selected caller up in the caller list.
Move down Moves the order of the selected caller down in the caller list.

For transitioning users: The order column displays only for bindings using the new namespace. If a binding with multiple callers was migrated to the new namespace, then the callers do not have an order. In that case, an error message is displayed. When this occurs, select a caller in the table and then click either Move up or Move down to assign an order to each caller. Callers must have orders assigned before you save the bindings or use the bindings with an application.trns

Caller identity local part

Local name of the caller to use for authentication. Enter a caller identity local name in this required field.

When specifying an LTPA caller, use LTPA as the local name for a caller that uses an older binding, prior to IBM WAS, V7.0. Newer bindings for IBM WAS, V7.0 and later should use LTPAv2 as the local name. Specifying LTPAv2 allows both LTPA and LTPAv2 tokens to be consumed, unless the Enforce token version option is selected on the token consumer.

Caller identity URI

URI of the caller to use for authentication. Enter a caller URI in this field.

When specifying an LTPA caller, use http://www.ibm.com/websphere/appserver/tokentype/5.0.2 as the URI for a caller that uses an older binding, prior to IBM WAS, V7.0. Newer bindings for IBM WAS, V7.0 and later should use the http://www.ibm.com/websphere/appserver/tokentype URI.

Use identity assertion

Whether identity assertion is used when authenticating. Select this check box to use identity assertion. Select this box to enable the Trusted identity local name and Trusted identity URI fields.

Trusted identity local name

Trusted identity local name when the identity assertion is used. Enter a trusted identity local name in this entry field when the identity assertion is used.

Trusted identity URI

Trusted identity uniform resource identifier (URI). Enter a URI in this entry field when the identity assertion is used.

Signing part reference

When the trusted identity is based on a signing token, select the signing part reference that represents the message parts signed by that token.

Callback handler

Class name of the callback handler. Enter the class name of the callback handler in this field.

JAAS login

Java Authentication and Authorization Service (JAAS) application login. We can enter a JAAS login, select one from the menu, or click New to add a new one.

For information on updating the Kerberos system JAAS login module for JAX-WS applications, read the topic Updating the system JAAS login with the Kerberos login module.

Custom properties – Name

Name of the custom property.

Custom properties are not initially displayed in this column. Select one of the following actions for custom properties:

Button Resulting Action
New Creates a new custom property entry. To add a custom property, enter the name and value.
Edit Specifies that we can edit the custom property value. At least one custom property must exist before this option is displayed.
Delete Removes the selected custom property.

Custom properties – Value

Value of the custom property that you want to use. Use the Value field to add, edit, or delete the value for a custom property.




 

Related tasks


Updating the system JAAS login with the Kerberos login module
Manage policy sets

 

Related


Caller collection
Set policy set bindings