Page History

KeyInfo is an optional element within the signature; it contains public key information needed to validate the signature. It is only applicable when performing an enveloped signature on POX or SAML (with WS-Security mode off). Select which options should be included within the KeyInfo element. The following options are available:

• X509 Certificate: Includes a X509Data/X509Certificate element containing the base64-encoded certificate. This is the recommended default.
• X509 IssuerSerial: Includes a X509Data/X509IssuerSerial element containing the X.509 name/serial number pair.
• X509 SKI: Includes a X509Data/X509SKI element containing the base64 encoded subject key identifier. The certificate must be X.509 version 3.
• X509SubjectName: Includes a X509Data/X509SubjectName element containing the X.509 subject name.
• Public KeyValue: Includes a KeyValue/RSAKeyValue element containing the base64-encoded public key.
• STR X509 Certificate: Includes a wsse:SecurityTokenReference/wsse:KeyIdentifier element containing the base64-encoded certificate.
• STR X509 SKI:  Includes a wsse:SecurityTokenReference/wsse:KeyIdentifier element containing the base64 encoded subject key identifier.

Enables signing SOAP messages according to OASIS WS-Security. The version of the OASIS standard can be configured in the Emulation Options Settings. By default, the content of the entire SOAP body will be automatically signed as configured in the Target Elements Settings. When this mode is disabled, an enveloped signature is performed on target elements.

Choose a setting from the Security header layout menu to specify which layout rules to apply when adding items to the WS-Security header. The following settings are available:

• Lax: Items are added to the security header in any order that conforms to WSS: SOAP Message Security.
• LaxTimestampFirst: Same as Lax, except that the first item in the security header MUST be a wsse:Timestamp.
• LaxTimestampLast: Same as Lax, except that the last item in the security header MUST be a wsse:Timestamp.
• Strict: Items are added to the security header following the numbered layout rules described below according to a general principle of 'declare before use'.

Enable Sign security token using STR Dereference Transform (STRDT) to automatically include the security token in the signature by referencing a security token reference (STR) using the STR Dereference Transform (STRDT) algorithm. By default, the signature will reference the STR that is automatically generated in the signature under the KeyInfo element. If a different STR should be referenced, such as an STR from the Security header, then include the STR in the Target Elements configuration.

Enable this option to sign a SOAP message based on the OASIS SAML Token profile or to perform an enveloped signature on a SAML assertion.

If the WS-Security mode option is disabled, an enveloped SAML signature will be formed on the SAML assertions selected under Target Elements Settings. SAML assertions using the holder-of-key confirmation method should typically have an enveloped signature.

If the WS-Security mode option is enabled, the SOAP envelope will be signed based on the OASIS SAML Token profile. You must choose the correct Emulation Option, otherwise the signature will not be successful:

.

Enable this option to reference the requester's keystore. This option is only applicable for SAML assertions using the holder-of-key confirmation method. This option should be disabled when the assertion does not have an enveloped signature, which is typical for sender-vouches confirmation.

If the WS-Security mode is disabled, the keystore can optionally be used to add the user's public KeyInfo into the assertion's subject confirmation before performing an enveloped signature on the SAML assertion. This is applicable for the holder-of-key scenario where the assertion holds the user's key and is signed by the assertion issuer.

If the WS-Security mode is enabled, the following requirements must be met in order for the signature on the SOAP message to be successful:

• 1. The holder-of-key assertion must hold the user's certificate referenced by this keystore. 
  2. The assertion in the SOAP header must already have an enveloped signature.

You can chain two XML Signers together to facilitate holder-of-key confirmation. Configure the first signer to add the public KeyInfo to the assertion's subject confirmation, then perform an enveloped signature on the assertion with the WSS mode off. Next, the second signer can sign the SOAP envelope containing the SAML assertion based on the OASIS SAML token profile with the WSS mode on.