Verify XML Document Action
<AMXMLVERIFY VERIFYUSING="text [options]" KEYCONTAINERNAME="text" KEYCONTAINERLEVEL="text [options]" />
Verifies whether 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.
Specifies the method in which to verify the XML document
The available options are:
KeyContainer - Specifies that the Windows key container which stores the private and public key requires a key container name.
KeyFile - Specifies either a .pri or .pfx file path. The .pri file is the file generated using Generate Key Files actions in Automate.
Note: These options appear only if you select the Key Container option from the Sign Using dropdown.
Allows you to enter the name of the key container to identify which private or public key to use. You select the key container by clicking on Select Key Container Button.
Specifies where the keys are stored in computer--either at the user or machine level.
The available options are:
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-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.
following two options are only available if you select the Key File option
Sign using dropdown.
Allows you to enter the path of the .pfx or .pri file on your system.
Allows you to enter the password used to during creation of private key (Usually used for .pfx file).
Specifies the session name to run the XML file in subsequent XML steps. This allows several connections to be active simultaneously.
This action includes the Description tab for entering a custom step description.
More on setting custom step description
This action also includes the standard Error Causes and On Error failure handling options/tabs.
More on Error Handling Options
All text fields allow the use of expressions, which can be entered by surrounding the expression in percentage signs (example: %MYVARIABLE%, %Left('Text',2)%). To help construct these expressions, you can open Expression Builder from these fields by pressing F2.
More on variables
More on expressions
More on the expression builder
NOTE: The code below can be copied and pasted directly into the Steps pane of the Task Builder.
<AMXMLVERIFY VERIFYUSING="KEYFILE" PUBKEYFILE="c:\sec.pub" />
<AMXMLVERIFY VERIFYUSING="KEYFILE" PUBKEYFILE="C:\Sing.pfx" PASSWORD="AM17o9+6JHieFc=aME" />