Configure Encrypted Passwords Using the LCU
The Connect:Direct® Secure Plus CLI displays passwords in plain text. If you need to encrypt passwords for use with the Connect:Direct Secure Plus CLI, use the Local Connection Utility (LCU) to create an LCU file that contains non-encrypted information used to encrypt the password and the encrypted password, such as a keycert passphrase. You can then refer to this file when prompted for passwords.
LCU Files
|
The use of the LCU syntax “LCU:” indicates that what follows is an LCU filename and not a passphrase. The pathname of the LCU file can be a relative path, a relative path to the bin directory, or a full path. If LCU:filename contains spaces, it must be enclosed in quotation marks: “LCU:filename”. The default name of the LCU file is cddef.bin. After the cddef.bin file is created, you can rename it as needed.
LCU files can be used to provide encrypted passwords for the following commands and parameters:
Command | Parameter |
---|---|
Update LocalNode | StsAuthKeyPairFilePassphrase StsSigKeyPairFilePassphrase SslTlsCertPassphrase |
Create RemoteNode | StsAuthKeyPairFilePassphrase StsSigKeyPairFilePassphrase SslTlsCertPassphrase |
Update RemoteNode |
StsAuthKeyPairFilePassphrase StsSigKeyPairFilePassphrase SslTlsCertPassphrase |
Create STSKeyPair |
Passphrase |
Update Client |
SslTlsCertPassphrase |
Update SEAServer |
SslTlsCertPassphrase |