On premise entry batch - encrypted credentials

In AVEVA Administration, you can compile credentials into an encrypted file. This allows you to create batch files without storing user credentials in plain text.

Store credentials in an encrypted file

1. To access this feature in Administration, select Manage, then select Users. At the bottom of this form, select Create Script.

   

   The Command Script Generation window opens:

   

   In this window, you can define the user credentials, MDB and conditions. The input field specifies the location of the macro to be executed, and the output field defines where the script is created.

2. (Optional) Select Conditions.

   The Command Script Conditions window opens:

   

   These optional conditions can specify which Windows users are allowed to start the macro, which physical machine can run the macro, and the time period during which the macro is valid.

   1. After entering desired options, select OK.

3. Select OK from the Command Script Generation window.

   If opened, encryptedmac.mac appears as follows. Viewing the file is not required.

   

   The resulting encrypted file contains the username, password, MDB, conditions and a call to the script at C:\Temp\example.mac, which in the following example contains the plain text script $P hello world.

4. Call the encrypted file from the following DOS script:

   ADMIN -module:Monitor -macro: c:\temp\encryptedmac.mac -tty

   The encrypted file opens and calls C:\Temp\example.mac.

   

Entry batch for LaaS – Unencrypted credentials

Firstly, there are a couple of environmental variable needs to be defined for the LaaS license server.

AVEVA_CONNECT_LOGIN = TRUE

AVEVA_LICENSE_SERVER_LIST = <URL pointing to License Server>

This is an indicator that LaaS is being used instead of AVEVA Licensing Service and will prompt all entries to AVEVA products to use LaaS.

DOS Batch LaaS – Encrypted credentials

The method for creating encrypted details is the same as used for non-LaaS on-premises projects.