Red Hat Bugzilla – Bug 1005334
Unable to login using smart card after adding the coolkey module to /etc/pki/nssdb
Last modified: 2013-11-21 18:06:13 EST
Description of problem:
Unable to login using smartcard after adding coolkey module to /etc/pki/nssdb. pklogin_finder shows an error load_pkcs11_module() failed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup kerberos for smartcard login.
2. Login to RHEL 6.5 Client machine using the smart card and check if the kerberos creds can be obtained.
3. Add the coolkey module to /etc/pki/nssdb/ as follows
modutil -add "CoolKey PKCS#11 Module" -dbdir /etc/pki/nssdb -libfile /usr/lib/pkcs11/libcoolkeypk11.so
4. Logout and try to select the smartcard login option.
The smart card login option cannot be selected. Login as local user and execute pklogin_finder debug, fails to recognize the card with error: load_pkcs11_module() failed
Should be able to login using smartcard and kerberos credentials should be valid
The basic problem is pk11install only works with paths, not sql: or dbm: paths.
When the build in the errata is installed, the PKCS#11 Coolkey Module is automatically added to /etc/pki/nssdb and smartcard login works fine.
If the PKCS#11 Coolkey Module is deleted and added back again, the issue described in this bug is seen (unable to login using smartcard)
Roshni, please to ls -s /etc/pki/nssdb
if pkcs11.txt does not have group other read, hand change it. There is an NSS bug against this issue.
I changed the permission of group other to read for the file pkcs11.txt, the issue still exists.
Roshni, can you point me to your machines that are misbehaving?
The machine is ready, you can have a look at the issue. Let me know if you need any more information from my side.
Coolkey seem seems to be working fine, the bug seems to be on the pam_pkcs11 component as in bug https://bugzilla.redhat.com/show_bug.cgi?id=1012082
this was ultimately not a coolkey bug, the fix was elsewhwere, so no docs needed for coolkey.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.