Sick error after successful login on /KMS key-manager.log shows 'com.chrysalisits.crypto.LunaException: LunaSession: slot uninitialized'
Originally Published: 2011-10-02
Article Number
Applies To
SafeNet Luna SA HSM
M-of-N is configured on SafeNet Luna partition
Activation and AutoActivation policies were enabled when SafeNet HSM partition was created
Issue
SafeNet command './vtl verify' works fine and shows list of slot(s) and partition(s)
"partition -show" command run on lunash:> prompt on Luna HSM shows Activation status as "no"
UNCONFIRMED: SafeNet command "hsm show" run on Lunash prompt on Luna SA shows "MofN activation status" as "Deactivated"
Cause
Resolution
service tomcat restart
Access to /KMS should now be successful.
In keyManagerServer.properties, make sure that provider.slot is set to the correct slot for your environment. This is located in /opt/KMS/conf/properties. If you need to change it, restart Tomcat for the change to take effect.
Workaround
Related Articles
Error "No appropriate protocol" in RSA Access Manager 6.2 45Number of Views After successful Account data collection, Custom Account Integer Attribute value is not displaying under Accounts tab in R… 21Number of Views Disabling weak ciphers using port 1813 in RSA Authentication Manager 8.3 patch 1 279Number of Views To generate FIPS compliant pkcs12 file using Openssl 39Number of Views FIM - Encryption Algorithms Q&A 28Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager Upgrade Process Running out of disk space when using RMAN in RSA Identity Governance & Lifecycle
Don't see what you're looking for?