We have created a smartcard extension based on CryptoTokenKit on macOS 10.13.
The smartcard logon does not always work well on macOS 10.13 GM Seed and macosx 10.12.6. I already filed a bugreport on this (https://bugreport.apple.com/web/?problemID=34276518)
On macos 10.13 beta 9, it works.
After successfully pairing and the screen saver is active, we can use the pin to login. But once the user has logged out and try to logon again using the smartcard, the system can not find the token driver. The log is given below;
2017-09-19 14:33:18.772185+0200 0x54ac Activity 0x7563 907 0 ctkd: (CoreFoundation) Loading Preferences From User CFPrefsD
2017-09-19 14:33:18.772746+0200 0x54ac Activity 0x7564 907 0 ctkd: (CoreFoundation) Sending Updated Preferences to User CFPrefsD
2017-09-19 14:33:18.779729+0200 0x54ab Activity 0x7565 907 0 ctkd: (PlugInKit) discovery
2017-09-19 14:33:18.799848+0200 0x54ac Activity 0x7566 907 0 ctkd: (Foundation) begin using plugin
2017-09-19 14:33:41.678279+0200 0x56fe Activity 0x7567 907 0 ctkd: (Security) SecItemDelete_ios
2017-09-19 14:33:41.696567+0200 0x56fe Activity 0x7568 907 0 ctkd: (CoreFoundation) Sending Updated Preferences to User CFPrefsD
2017-09-19 14:33:41.698188+0200 0x5790 Activity 0x7569 907 0 ctkd: (CoreFoundation) Loading Preferences From System CFPrefsD For Search List
2017-09-19 14:33:41.698263+0200 0x5790 Activity 0x756a 907 0 ctkd: (CoreFoundation) Loading Preferences From User CFPrefsD For Search List
2017-09-19 14:33:42.137638+0200 0x5790 Activity 0x756b 907 0 ctkd: token inserted
2017-09-19 14:33:42.138165+0200 0x5790 Activity 0x756c 907 0 ctkd: (PlugInKit) discovery
2017-09-19 14:33:42.229946+0200 0x5791 Activity 0x756d 907 0 ctkd: (Foundation) begin using plugin
2017-09-19 14:33:42.241138+0200 0x5790 Default 0x756d 907 0 ctkd: [com.apple.CryptoTokenKit.token] com.somecompany.bfesce cannot handle token in slot SCM Microsystems Inc. SCR 3311, error:(null)
2017-09-19 14:33:42.241962+0200 0x5790 Error 0x756c 907 14 ctkd: [com.apple.CryptoTokenKit.token] No token driver found for card <TKSmartCardATR: 0x7fec7ec11420 3b 1800ff T=1:--- T=1:fe45-;43...> ATR bytes: <3b...
Could it be that it has something to do with the way the smartcard extension has been registered?
We put the smartcard extension under the folder PlugIns/ inside our main app which serves as a host.