Table of Contents
Advertisement
3.7.2. Events
• Simple events such as card insertions and removals, successfully completed operations, card
operations that result in an error, and similar events.
• Errors are reported from the TPS to the Enterprise Security Client.
• The NSS crypto library is initialized.
• Other low-level smart card events are detected.
3.7.3. Information about the Smart Card
The Diagnostics Information screen displays the following information:
• The Enterprise Security Client version number.
• The version information for the Xulrunner framework upon which the client is running.
• The number of cards detected by the Enterprise Security Client.
For each card detected, the following information is displayed:
• The version of the applet running on the smart card.
• The alpha-numeric ID of the smart card.
• The card's status, which can be any of the three things:
• NO_APPLET No key was detected.
• UNINITIALIZED. The key was detected, but no certificates have been enrolled.
• ENROLLED. The detected card has been enrolled with certificate and card information.
• The card's Phone Home URL. This is the URL from which all Phone Home information is obtained.
• The card issuer name, such as Example Corp.
• The card's answer-to-reset (ATR) string. This is a unique value that can be used to identify different
classes of smart cards. For example:
3BEC00FF8131FE45A0000000563333304A330600A1
• The TPS Phone Home URL.
• The TPS server URL. This is retrieved through Phone Home.
• The TPS enrollment form URL. This is retrieved through Phone Home.
• Detailed information about each certificate contained on the card.
• A running log of the most recent Enterprise Security Client errors and common events.
Events
37
Advertisement
Table of Contents
