[XrcXUDADUNABLE]: unable to contact directory server
Originally Published: 2003-01-10
Article Number
Applies To
Keon Key Recovery Module 6.5
Sun Solaris 2.8
nCipher
Issue
An error ([XrcXUDADUNABLE]: unable to contact directory server) was encountered in generating your encryption certificate. If the cause of the problem is not evident, you will need to contact the administrator of this system to proceed further.
Cause
Resolution
1. The OCS for the jurisdiction is still active (which means one of the cards in the cardset is still inserted) and the CA is not correctly noticing that it is not supposed to do "Prompt every time" (see below)
2. The OCS in use has been configured for persistent and the keys previously unlocked
An easy test to confirm if your CA (and its cardset) is correctly configured is to do check the following:
1. Enroll for a certificate
2. Approve it
3. Enroll for another certificate
4. Approve it
Question - how many times did you need to type in your PIN(s) for the OCS? If your answer is more than once, the CA is not configured correctly, as this would mean that at the point in time when the end-user tries to get the CA to create and download the encryption certificate that the CA is not going to have access to its keys (and generates the error message).
For more information, see the solution regarding [XrcXUDADUNABLE]: unable to contact directory server.
Related Articles
RSA Authentication Manager 7.1 to 8.1 - Upgrading an Existing Hardware Appliance 3.0 Number of Views How to troubleshoot CT-KIP failures in Authentication Manager 8.x Number of Views Troubleshooting SAML Authentications with the RSA Cloud Authentication Service as Identity Provider Number of Views Add a RADIUS Attribute Definition to a Dictionary Number of Views Deep Links for token import fails on Android 12 Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process RSA Authenticator 6.2.2 for Windows Administrator Guide RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows
Don't see what you're looking for?
