Encrypting Sensitive INI File Data for the Deployment Server and EnterpriseOne Windows Client Machines

If you are using a site key for the encryption of INI file data in other EnterpriseOne Server configuration files, you can use the same site key to encrypt the password in the following WRIPassword setting in the JDE.INI files used by the Deployment Server and EnterpriseOne Windows clients:

[WORKFLOW]
WRIPassword=

To encrypt the data in this setting in the JDE.INI on the Deployment Server:

Copy the JDE.INI, typically located at C:\Windows\JDE.INI, into a temporary folder.
If the WRIPassword setting is blank, add the plain-text password.
From the JDE.INI of the Security Server, copy the [SITE_KEYS] block with all of its key values into the JDE.INI used by the Deployment Server. The JDE.INI file is typically located at C:\Windows\JDE.INI.
Use the following command for each INI file to convert the passwords to the latest encryption:
E1IniEncrypt -<options> <path to ini>
Where <options> include:
```
        -jde    : Encrypt passwords in JDE.INI
        -inter  : Encrypt passwords in JDEINTEROP.INI
        -jas    : Encrypt passwords in JAS.INI
        -jdbj   : Encrypt passwords in JDBJ.INI
        -tok    : Encrypt passwords in TOKENEGEN.INI
```
And where <path to ini> is the path to the temporary folder containing the INI files.
Verify that the value in the WRIPassword setting has been encrypted with the Tools 9.2 encryption (which begin with "AD"). The remainder of the JDE.INI should remain unchanged.
Copy the JDE.INI from the temporary folder back to its original location.

For the JDE.INI to be used by the EnterpriseOne Windows clients, follow the same steps as above, but copy and convert the JDE.INI located in the Windows client installation folder on the Deployment Server. This installation folder contains the JDE.INI that is used for the installation of new Windows clients.