Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-7729: Pin prompt never appears after inserting smart card on RHEL 5.10/11

Centrify DirectControl ,  

14 November,16 at 05:18 PM

Applies to:

All Versions of Centrify DirectControl on RHEL 5.10 and RHEL 5.11


Problem:

On RHEL 5.10 and 5.11, if "Smart Card Support" is enabled and a smart card is inserted on the login screen, a PIN prompt may not show up until after the "Enter" key is hit.


Cause:

There are issues with the gdm and nss packages in RHEL 5.10 and 5.11, particularly the libsoftokn3.so library that does not allow the PIN prompt to appear.


Workaround:

Replace libsoftokn3.so with the old one on RHEL 5.9, which is a shared object file in NSS package

The version of NSS from RHEL 5.9 is:
nss-3.13.5-8.el5

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-2466: No PIN prompt when using Smart Card articleKB-1617: Troubleshooting smart card issues on Mac systems articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-3925: How to add Centrify parameter to a group policy articleKB-7730: Screen locks after successful login without pulling smart card on RHEL 5.10/11 articleKB-7159: Smartcard login not working on system that has been hardened articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6041: How to show current license type in use by adclient? articleKB-6040: How to change the license type in use after adclient successful joined to the AD?