Shawn,
The point is none of the applications using the Keychain APIs reject certificates stored on the token or handle them improperly except for VPN client.
The first thing I'd like to know, does anybody have positive experience with using certificates stored on token in built-in VPN client on MacOSX 10.9.
If does, what tokend is used? Has anybody tried using PKCS11.tokend?
Moreover, I wonder why PKCS11.tokend is cut out of tokend installers.
By the way, rather long ago I've reported the issue with Apple Bug Reporter (ticket 15654874), it is still open and marked as a duplicate.
Best regards,
Eugene Mironenko
написал(а):
On Mar 12, 2014, at 5:29 AM, Мироненко Евгений <
mironenko@rutoken.ru> wrote:
- Shawn_____________________________________________________________________
Hello!
I'm using Gemalto Tokend to access the certificates on the token. On Mac OS X 10.8 the certificates on the token are accessible via Keychain Access, Mail utilities and built-in VPN client, but after updating to 10.9 I've got an issue that certificates on the token are not listed in built-in VPN client (when selecting authentication parameters) though they are visible in Keychain Access utility.
Is it a problem with Tokend used or Apple has just cut out tokend support from VPN client? Is there any workaround for the issue?
Best regards,
Eugene Mironenko
Eugene,
Nothing has changed architecturally from the Apple side on Tokend or on the ability of any Apple services (ie. VPN) to utilize the Keychain APIs which is how they get access to Smart Cards supported with a Tokend. Have you updated the Tokend for 10.9 using the updated installers posted ? There was a security CVE addressed and implemented in the new updates as well.
Please capture logs before and during the transactions and submit with a ticket, so we can look into it. We may uncover something from there.
-Shawn