I am experiencing the same issues here. My SCM 3310 worked perfectly on 10.5.5 but the recent update to 10.5.6 now makes me SCM 3310 CAC Reader totally unrecognizable (brief green light when I plug-in but then dead - does not even show up in keychain anymore).
Working from the Apple post at http://lists.apple.com/archives/Fed-talk/2008/Dec/msg00093.html provided NO SOLUTION. My reader's firmware is the newest version from SCM and per msg00093 (and the attached link to Open Source author's CCID supported CAC Readers - http://pcsclite.alioth.debian.org/ccid.html) specifically states that SCM 3310 is suported.
Apple support is requested on this item as it has impacted nearly a dozen DoD Mac users at my station (which makes it hard to sing the praises of Mac when every update seems to cripple usability). I hate to revert to 10.5.5 and ignore all future OS X updated but MUST be able to use my CAC at home. If anyone has solved this issue please post the steps to fix the matter; any help is appreciated.
V/r
Matt
Working from the Apple post at http://lists.apple.com/archives/Fed-talk/2008/Dec/msg00093.html provided NO SOLUTION. My reader's firmware is the newest version from SCM and per msg00093 (and the attached link to Open Source author's CCID supported CAC Readers - http://pcsclite.alioth.debian.org/ccid.html) specifically states that SCM 3310 is suported.
Apple support is requested on this item as it has impacted nearly a dozen DoD Mac users at my station (which makes it hard to sing the praises of Mac when every update seems to cripple usability). I hate to revert to 10.5.5 and ignore all future OS X updated but MUST be able to use my CAC at home. If anyone has solved this issue please post the steps to fix the matter; any help is appreciated.
V/r
Matt
Oct 05, 2018 First, confirm that you see your CAC ID within the Keychains section on the left side of the Keychain Access window. Next, if you are using Safari v12, this version has problems using smart card certificates, both with PKard and Apple's smartcard services. This is called SSL client side certificate. Sites can make the browser generate a keypair for you. Then they’ll sign your public key using their private key and they’ll be able to securely identify you from then on. Here is a Common problems and solutions page for specific error codes. If the certificate warning message still appears when you attempt to log in to Cisco Jabber for MAC, click the Show certificate button in order to find more details on the certificate presented, and collect a problem report.
![Client Client](/uploads/1/2/6/4/126432913/190934649.png)
Cac No Client Certificate Presented
Jan 6, 2009 6:13 AM