Supporting Token Assertion | Add to a WS-Policy to... |
<sp:SupportingTokens> | Identify the tokens to use to populate the <Supporting Tokens> property. Supporting tokens are included in the security header and can optionally include additional message parts to sign or encrypt. Integration Server supports the following nested assertions: <sp:AlgorithmSuite> <sp:SignedParts> <sp:SignedElements> <sp:EncryptedParts> <sp:EncryptedElements> |
<sp:SignedSupportingTokens> | Include signed tokens in the message signature and can optionally include additional message parts to sign and/or encrypt. Integration Server supports the following nested assertions: <sp:AlgorithmSuite> <sp:SignedParts> <sp:SignedElements> <sp:EncryptedParts> <sp:EncryptedElements> |
<sp:Endorsing SupportingTokens> | Sign the message signature and can optionally include additional message parts to sign and/or encrypt. Integration Server supports the following nested assertions: <sp:AlgorithmSuite> <sp:SignedParts> <sp:SignedElements> <sp:EncryptedParts> <sp:EncryptedElements> |
<sp:SignedEndorsing SupportingTokens> | Sign the token used for the message signature and are also signed by the signed endorsing token and can optionally include additional message parts to sign and/or encrypt. Integration Server supports the following nested assertions: <sp:AlgorithmSuite> <sp:SignedParts> <sp:SignedElements> <sp:EncryptedParts> <sp:EncryptedElements> |
<sp:SignedEncrypted SupportingTokens> | Include supporting tokens in the security header that are also encrypted when they appear in the security header. Make sure that the tokens are encrypted in order to guarantee token confidentiality. Integration Server supports the following nested assertions: <sp:AlgorithmSuite> <sp:SignedParts> <sp:SignedElements> <sp:EncryptedParts> <sp:EncryptedElements> |
<sp:Encrypted SupportingTokens> | Include supporting tokens in the security header that are also encrypted when they appear in the security header. Note: WS-SecurityPolicy 1.2 only. The sp:EncryptedSupportingTokens element should be used only when you cannot provide the “message signature”. Make sure that the tokens are encrypted in order to guarantee token integrity and confidentiality. Integration Server supports the following nested assertions: <sp:AlgorithmSuite> <sp:SignedParts> <sp:SignedElements> <sp:EncryptedParts> <sp:EncryptedElements> |
<sp:EndorsingEncrypted SupportingTokens> | Include endorsing supporting tokens that are also encrypted when they appear in the security header. Make sure that the tokens are encrypted in order to guarantee token confidentiality. Note: WS-SecurityPolicy 1.2 only. Integration Server supports the following nested assertions: <sp:AlgorithmSuite> <sp:SignedParts> <sp:SignedElements> <sp:EncryptedParts> <sp:EncryptedElements> |
<sp:SignedEndorsingEncrypted SupportingTokens> | Include signed, endorsing supporting tokens that are also encrypted when they appear in the security header. Make sure that the tokens are signed and encrypted in order to guarantee token confidentiality. Integration Server supports the following nested assertions: <sp:AlgorithmSuite> <sp:SignedParts> <sp:SignedElements> <sp:EncryptedParts> <sp:EncryptedElements> |