The <auth_token_type> element
Specifies what type of identity token is required.
This element is mandatory when you specify the <sts_authentication> element
in a service requester pipeline, and optional in a service provider.
- In a service requester pipeline, the <auth_token_type> element indicates the type of token that STS issues when CICS® sends it the user ID contained in the DFHWS-USERID container. The token that CICS receives from the STS is placed in the header of the outbound message.
- In a service provider pipeline, the <auth_token_type> element
is used to determine the identity token that CICS takes from the message header and sends
to the STS to exchange or validate. CICS uses
the first identity token of the specified type in the message header.
If you do not specify this element, CICS uses
the first identity token that it finds in the message header. CICS does not consider the following
as identity tokens:
- wsu:Timestamp
- xenc:ReferenceList
- xenc:EncryptedKey
- ds:Signature
Used in:
- Service provider
- Service requester
Contained by:
Contains:
- A <namespace> element. This element contains
the namespace of the token type that is to be validated or exchanged.
If you are using SAML, set the content of this element to either urn:oasis:names:tc:SAML:1.0:assertion or urn:oasis:names:tc:SAML:2.0:assertion, depending on the version of SAML.
- An <element> element. This element contains
the local name of the token type that is to be validated or exchanged.
For SAML, use the local name Assertion.
Example
<auth_token_type>
<namespace>http://example.org.tokens</namespace>
<element>UsernameToken</element>
</auth_token_type>