Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices
Here are some basic checks to make when troubleshooting smart card services.
Are the smart card readers configured? See Section 8.6.1, “How to Configure Primary Smart Card Readers for Hotdesking and Authentication” or Section 8.6.2, “How to Configure External CCID-Compliant USB Smart Card Readers for Authentication (Oracle Solaris)” for details.
Is the expected smart card bus protocol configured? See Section 8.6.5, “How to Change the Smart Card Bus Protocol (Oracle Solaris)” for details.
Are the appropriate smart card configuration files available? See Section 8.6.3, “How to Add a Smart Card Configuration File” for details.
Is the expected smart card probe order configured? See Section 8.6.4, “How to Change the Smart Card Probe Order” for details.
Check for any core dumps in the
/tmp/SUNWut/pcscd directory.
Here are some guidelines and workarounds when using authenticated smart cards.
When a smart card transaction is occurring on a Sun Ray Client (smart card LED is flashing), avoid hotdesking or resetting the Sun Ray Client. If a problem occurs, you may have to log out of the session.
If you reset a Sun Ray Client that has smart card-related applications currently running, the applications may freeze for up to two minutes or the smart cards may be inaccessible for up to two minutes. The applications should recover without user intervention.
When hotdesking with a Windows connector session running, the PIN dialog may fail to display. You will get a password prompt. If this happens, log out of the Windows session, restart the Windows connector session, and log into Windows again.
When rapidly hotdesking a Sun Ray Client, it may fail to recognize the smart card and OSD icon 63 will display instead of the session. Remove and reinsert the card to resolve the issue.
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices