"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 Identity Governance and Lifecycle Access Fulfillment Express (AFX) Server fails to start with error: An issue with han… Number of Views Performance issue with Change Request generation from a Review to Revoke a large volume of access in RSA Identity Governan… Number of Views Using Vault instead of cleartext password in WildFly configuration file in RSA Identity Governance & Lifecycle Number of Views How to remove RSA ACE/Server node secret when RADIUS is in use and no RSA ACE/Agent is installed Number of Views Functionality requiring the retrieval of encrypted passwords is failing after a database restore in RSA Identity Governanc… Number of Views
Trending Articles
How to Download OTP Token Seed Files from myRSA RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8
Don't see what you're looking for?
