Rishi Renjith wrote: > Yes, the RSA private keys as well as the certificates are stored in the > keystore in the card. See below . > /*bash-3.00# certutil -K -d .* > certutil: Checking token "NSS Certificate DB" in slot "NSS User Private Key > and Certificate Services" > Enter Password or Pin for "NSS Certificate DB": > certutil: no keys found > *bash-3.00# certutil -K -d . -h "Sun Software PKCS#11 softtoken"* > certutil: Checking token "Sun Software PKCS#11 softtoken" in slot "Sun > Crypto Softtoken" > Enter Password or Pin for "Sun Software PKCS#11 softtoken": > certutil: no keys found > *bash-3.00# certutil -K -d . -h "Sun Metaslot"* > certutil: Checking token "Sun Metaslot" in slot "Sun Metaslot" > Enter Password or Pin for "Sun Metaslot": > < 0> rsa //204a23dbb2e82d7d8c1495e3374dcd//4462423e4c Sun > Metaslot:cert309 > < 1> rsa //54ea6d93df1cfef13064aedc6f6c7f//0dce34e7b6 Sun > Metaslot:cert147 > < 2> rsa //34d4a4974cf325e735dd23bb3a6b46//80249f3550 (orphan) > < 3> rsa //2018eecb4c05eb25cd30be4de6f13c//caeadcb43d Sun > Metaslot:cert1151 > < 4> rsa //61932a2d796fd8f6e82949059176e9//80cde5c55a sanCert > < 5> rsa //4e752a9b4a76c1462d9aec76de1617//e08d07ff42 Sun > Metaslot:ismc_cert /
what is the output of: $ cryptoadm list metaslot Does it look exactly like this: System-wide Meta Slot Configuration: ------------------------------------ Status: enabled Sensitive Token Object Automatic Migrate: enabled Persistent object store slot: Sun Crypto Softtoken Persistent object store token: Sun Software PKCS#11 softtoken It shouldn't because I see from an earlier email that you did run "cryptoadm enable metaslot token=ks". Was that run before the application was started ? Please also show the output of: $ pktool list $ pktool list token=ks objtype=both That assumes your Token name is 'ks'. $ cryptoadm list -p -- Darren J Moffat
