Valid and Default Card Types for Client Applications

Two card properties designate which smart card types the user must use to log in to a particular client application, or to all client applications on the system: defaultcard and validcards.

The validcards property specifies all smart card types that are valid for a particular application. In contrast, the defaultcard tells the application to wait until the card defined as the default card is loaded into the reader.

For example, suppose you specify iButton, Cyberflex, and CardA as the validcards properties for Application B. Then you specify Cyberflex as the defaultcard property. If Application B accepts only its default card and the user tries to log in to Application B with CardA, then the system displays the message:

Waiting for Default Card

Login to Application B is blocked until the user inserts a Cyberflex card into the reader.

When you run smartcard -c admin, these values are displayed:

default.validcards        = CyberFlex IButton PayFlex

See "How to Change the Valid Smart Cards for a Client Application (Command Line)" and "How to Assign a Default Smart Card to a Client Application (Command Line)" for step-by-step instructions on changing these properties.