Generates public and private key files from the specified key container. This action can be used as a task step following Create Key Container action to properly generate public and private key files. Other cryptography actions (i.e. Sign and Encrypt actions) can follow this step allowing the procedure of encrypting and decrypting files to be fully automated.
Declaration
<AMGENERATEKEYFILES KEYCONTAINERNAME="Filename"KEYCONTAINERLEVEL="text [options]" PRIKEYFILE="Keyname" PUBKEYFILE="Keyname"/>
Example 1 - Generate USER Level Key Files
<AMDELETEKEYCONTAINER KEYCONTAINERNAME="marie.black" KEYCONTAINERLEVEL="USER" />
Example 2 - Generate MACHINE Level Key Files
<AMDELETEKEYCONTAINER KEYCONTAINERNAME="JavaWebStart" KEYCONTAINERLEVEL="MACHINE" />
See Also: Delete Key Container, Sign, Verify, Encrypt, Decrypt
|
Property |
Type |
Required |
Default |
Markup |
Description |
|
Key Container Name |
Text |
Yes |
(Empty) |
KEYCONTAINERNAME="Automate" |
Specifies the name of the key container to identify which public/private key to use. Clicking Select Key Container will open a key container browser in which to select a container from. |
|
Key Container Level |
Text (Options) |
Yes |
User |
KEYCONTAINERLEVEL="MACHINE" |
Specifies whether to use a machine-level or user-level RSA key container. Microsoft Windows makes machine-level key containers available to all users, whereas a user-level key container is available only to the user that created (or imported) the key container. This parameter is active only if the Decrypt using parameter is set to Key Container. The available options are:
|
|
Public key file |
Text |
Yes |
(Empty) |
PUBKEYFILE="c:\publicfile.pub" |
Specifies the path and file name of the public key to be generated. |
|
Overwrite if public key file exists |
Yes/No |
No |
No |
OVERWRITEPUBKEYFILE="YES" |
If set to YES, Indicate that if a public key file with the same name already exists within the location where the new public key will be stored, the existing key will be overwritten. |
|
Private key file |
Text |
Yes |
(Empty) |
PRIKEYFILE="c:\privatefile.pri" |
Specifies the path and file name of the private key to be generated. |
|
Overwrite Private key file |
Yes/No |
No |
No |
OVERWRITEPRIKEYFILE="YES" |
If set to YES, indicate that if a private key file with the same name already exists within the location where the new private key will be stored, the existing key will be overwritten. |
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.