"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
Checkpoint bandwidth report showing incorrect KBytes information Number of Views Abend in stored procedure when executing non-XPlink DLL on z/OS Number of Views How to uninstall RSA Identity Governance & Lifecycle Number of Views Using Vault instead of cleartext password in WildFly configuration file in RSA Identity Governance & Lifecycle Number of Views Uninstall a Web Tier on Windows Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Release Notes for RSA Authentication Manager 8.8 RSA RADIUS Server service failed to start in the RSA Authentication Manager 8.1 Operations Console Microsoft Entra ID External MFA - Relying Party Configuration Using OIDC - RSA Ready Implementation Guide RSA Release Notes: Cloud Access Service and RSA Authenticators
Don't see what you're looking for?
