Description

Verifies that the signature of the specified XML file is still valid. If the XML file has been signed, this action will detect a modification to that XML file that invalidates the signature.

Declaration

<AMXMLVERIFY VERIFYUSING="text [options]" KEYCONTAINERNAME="text" KEYCONTAINERLEVEL="text [options]" />

Example

<AMXMLVERIFY VERIFYUSING="KEYFILE" PUBKEYFILE="c:\sec.pub" />

<AMXMLVERIFY VERIFYUSING="KEYFILE" PUBKEYFILE="C:\Sing.pfx" PASSWORD="AM17o9+6JHieFc=aME" />

General Tab Parameters

Verify using: Tells the system how you want verify the signature from the in-memory XML file.

• KeyContainer - Specifies that the Windows key container, which stores the private and public key.

• KeyFile - Specifies either a .pri or .pfx file path. The .pri file is the file generated using Generate Key Files actions in Automated Workflow.

Text [Options], optional, default "KeyContainer"
MARKUP: VERIFYUSING="Keyfile"

Key container name: Allows you to enter the name of the key container to identify which private or public key to use. Specify the key container by clicking Select Key Container.

Text, Required
MARKUP: KEYCONTAINERNAME="Automated Workflow"

Key container level: Specifies where the keys are stored in computer:

• User: User-level RSA key containers are stored with the Windows user profile for a particular user and can be used to encrypt and decrypt information for applications that run under that specific user identity. User-level RSA key containers can be useful if you want to ensure that the RSA key information is removed when the Windows user profile is removed. However, because you must be logged in with the specific user account that makes use of the user-level RSA key container in order to encrypt or decrypt protected configuration sections, they are inconvenient to use.

• Machine: Machine-level RSA key containers are available to all users that can log in to a computer, by default, and are the most useful as you can use them to encrypt or decrypt protected configuration sections while logged in with an administrator account. A machine-level RSA key container can be used to protect information for a single application, all the applications on a server, or a group of applications on a server that run under the same user identity. Although machine-level RSA key containers are available to all users, they can be secured with NTFS Access Control Lists (ACLs) so that only required users can access them.

Link: http://msdn2.microsoft.com/en-us/library/f5cs0acs.aspx

Text [Options], optional, default "User"
MARKUP: KEYCONTAINERLEVEL="Machine"

Session name: Specifies the session name to run the XML file in subsequent XML steps. This allows several connections to be active simultaneously.

Text, Optional - default "XMLSession1"
MARKUP: SESSIONNAME="FirstXMLSession"

The following two options are only available if you choose Key File option for Sign using.

Public key file: Allows you to enter the path of the .pfx or .pri file on your system.

Text, Required
MARKUP: KEYPAIRFILE="c:\secret.pri"

Password: Allows you to enter the password used to during creation of private key (Usually used for .pfx file).

Text, Optional
MARKUP:  PASSWORD="password"

See Also

Validate XML File Action, Sign XML File Action