Interesting; it did not: # pet105:~> modutil -dbdir /var/lib/subca01/alias/ -nocertdb -list Listing of PKCS #11 Modules ----------------------------------------------------------- 1. NSS Internal PKCS #11 Module slots: 2 slots attached status: loaded slot: NSS Internal Cryptographic Services token: NSS Generic Crypto Services slot: NSS User Private Key and Certificate Services token: NSS Certificate DB 2. CryptoServer library name: /usr/bin/libcs2_pkcs11.so slots: 1 slot attached status: loaded slot: CryptoServer Device '/dev/cs2' - Slot No: 0 token: CBUAETEST ----------------------------------------------------------- # pet105:~> TokenInfo /var/lib/subca01/alias Database Path: /var/lib/subca01/alias Found external module 'NSS Internal PKCS #11 Module' # pet105:~> And there were no SELinux errors in the audit log. Arshad Noor StrongAuth, Inc. Chandrasekar Kannan wrote:
Looks like the NSS layer has no problems identifying the token. can you use this tool and see if the JSS layer can see it as well ?
http://www.redhat.com/docs/manuals/cert-system/8.0/cli/html/TokenInfo.html