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-7730: Screen locks after successful login without pulling smart card on RHEL 5.10/11

Centrify DirectControl ,  

14 November,16 at 05:17 PM

Applies to:

All Versions of Centrify DirectControl on RHEL 5.10/11


Problem:

On RHEL 5.10/11, if "Smart Card Support" is enabled and "Card Removal Action" is configured as "Lock", the screen will be locked several seconds after a successful login with smart card.


Cause:

There are issues with RHEL gdm and nss packages in RHEL 5.10 and 5.11.

Libcentrifypkcs11.so has been configured to let apps access the smart card and is loaded into /etc/pki/nssdb/secmod.db.

When an app wants to access the smart card, it will check to see if libcentrifypkcs11.so exists in the secmod.db by using the nss librarry libsoftokn3.so.

On RHEL 5.10/11, libsoftokn3.so cannot open /etc/pki/nssdb/secmod.db, even though it exists.

This will cause the app to think that the smart card is unplugged and when the Group Policy "Lock Smart Card screen for RHEL" is enabled, and gnome-screensaver finds "smart card unplugged", it will do a screen lock. Thus causing this issue to happen.


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-7415: Unable to unlock screen with Smart Card on RHEL 7 articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6041: How to show current license type in use by adclient? articleKB-3925: How to add Centrify parameter to a group policy articleKB-7729: Pin prompt never appears after inserting smart card on RHEL 5.10/11 articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin?