Caller [Settings]

Specifies the security token, signed part or encrypted part used for authentication. If a signed or encrypted part is used, the value of the part attribute must be the name of a defined required integrity or required confidentiality constraint. If a standalone security token is used for authentication, then the URI and local name attributes must define the type of security token used for authentication.

To view this pane in the console, click the following path:

Service integration > Web services > WS-Security configurations > v1-inbound-config_name > [Request consumer] Caller > caller_name .

Configuration tab

The Configuration tab shows configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.

General Properties

Name

The name of the caller.

Required Yes
Data type Text

Part

Specifies the name of the required integrity or required confidentiality part within the message to be used for authentication.

Required No
Data type drop-down list

URI

Specifies the namespace URI of the security token to be used for authentication.

If you specify a Username token or X.509 certificate security token, you do not have to specify a URI. If you specify a custom token, enter the URI of the QName for the value type. If you specify Lightweight Third Party Authentication (LTPA), enter the following WebSphere® Application Server predefined value type URI: http://www.ibm.com/websphere/appserver/tokentype/5.0.2. If you specify Lightweight Third Party Authentication propagation (LTPA_PROPAGATION), enter the following WebSphere Application Server predefined value type URI: http://www.ibm.com/websphere/appserver/tokentype.

Required No
Data type Text

Local name

Specifies the local name of the security token to be used for authentication.

WebSphere Application Server has the following predefined local name value types:
Username token
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken
X509 certificate token
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3
# X509 certificates in a PKIPath
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509PKIPathv1
A list of X509 certificates and CRLs in a PKCS#7
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#PKCS7
LTPA
For Lightweight Third Party Authentication, the local name value type is LTPA.
LTPA_PROPAGATION
For Lightweight Third Party Authentication token propagation, the local name value type is LTPA_PROPAGATION.
Attention:
  • If you enter LTPA in the Local name field, you must also specify the URI value http://www.ibm.com/websphere/appserver/tokentype/5.0.2 in the URI field.
  • If you enter LTPA_PROPAGATION in the Local name field, you must also specify the URI value http://www.ibm.com/websphere/appserver/tokentype in the URI field.
  • If you enter any of the other predefined local name value types, you can leave the URI field blank. For example, to specify "Username token", enter http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken in the Local name field and do not enter a value in the URI field.
  • If you specify a custom value type for a custom token, you must specify the local name and the URI of the Quality name (QName) of the value type. For example, you might enter Custom in the Local name field, and http://www.ibm.com/custom in the URI field.
Required No
Data type Text

Additional Properties

Trust method
The trust method associated with this caller if IDAssertion is in use for verifying an asserted ID from an intermediary.
Properties
Properties associated with the caller.


Terms of Use | Feedback

Last updated: Oct 21, 2010 7:37:48 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=ReqConCaller_DetailForm
File name: ReqConCaller_DetailForm.html