...
| Key Store | Select the Key Store used to verify your identity and to sign the XML data from the Key Store menu. The Key Stores available in this menu are dependent on the Key Stores you added at the test or Responder suite level.For more information on adding Key Stores, see Adding Global Key Stores in SOAtest and Adding Global Key Stores in Virtualize. |
|---|---|
| Algorithm | Specifies the unique algorithm used for defining the certificate keys. |
| Digest method | Choose a message digest algorithm for signing the data. |
| Canonical form | Specifies the algorithm used to create a canonicalized form of the information being signed. |
| KeyInfo form | 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:
|
| WS-Security mode | Enables signing SOAP messages according to OASIS WS-Security. 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:
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. |
| Perform SAML signature | 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. |
| User Key Store | 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:
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. |
...
- Text: Use this option if you want to type or copy the XML document into the UI. Select the appropriate MIME type, enter the XML in the text field below the Text option.
- File: Use this option if you want to use an existing file. Click Browse to choose a file.
Enable Persist as Relative Path if you want the path to this file to be saved as a path that is relative to the current configuration file. Enabling this option makes it easier to share tools across multiple machines. If this option is not enabled, the test or Responder will save the path to this file as an absolute path.
Usage Notes
You can use the XML Signer tool as a standalone tool at the tool level by right-clicking the main test suite node and selecting Add New > Test, then selecting XML Signer from the dialog that opens. You can also chain the XML Signer tool to a messaging tool by right-clicking the desired tool node and selecting Add Output, then selecting XML Signer from the dialog that opens.You can chain the XML Signer tool to a messaging tool by right-clicking the desired tool node and selecting Add Output, then selecting XML Signer from the dialog that opens. The messaging tool will use the transformed XML.
...
| Info | ||
|---|---|---|
| ||
| In order to perform security operations using the XML Signature Verifier, XML Signer, or XML Encryption tools, or if using Key Stores, you will need to download and install the Unlimited Strength Java Cryptography Extension. For details, see JCE Prerequisite. |
Related Tutorials
The following tutorial lesson demonstrates how to use this tool:
...