"Invalid Lockbox Configuration File" caused by space after masterpassword in server configuration files
Originally Published: 2015-10-15
Article Number
Applies To
Lockbox and cryptedit applications
Issue
When a space is inadvertently configured after the keyitem in the parameter "cleartrust.configuration.lockbox.items.masterpassword=" this will cause the following error to be thrown when running cryptedit to create the enc files.
"Invalid Lockbox Configuration File."
Cause
Resolution
You will also have to delete the encrypted parameter file (*.enc) that was created with the misconfigured keyitem
This file can be found by referencing the following parameter:
cleartrust.configuration.encrypted_store=
Summary of parameters referenced in this document
cleartrust.configuration.lockbox.items.masterpassword=
cleartrust.configuration.encrypted_store=
The above parameters are found in the following Access Manager Server configuration files
• aserver.conf
• eserver.conf
• dispatcher.conf
• keyserver.conf
Related Articles
RSA Authenticator 4.4 for iOS and Android Administrator Guide Number of Views Using Vault instead of cleartext password in WildFly configuration file in RSA Identity Governance & Lifecycle Number of Views Authentication to remote Active Directory fails in RSA Governance and Lifecycle when auto select is unchecked Number of Views RSA Identity Governance and Lifecycle Access Fulfillment Express (AFX) Server fails to start with error: An issue with han… Number of Views Errors 'Server Timeout' and 'User TIME's access is denied' with RSA Access Manager and RSA SecurID Number of Views
Don't see what you're looking for?
