SmartCardReader PCSC

The ComponentEnable and ComponentDisable are used as a whitelist/blacklist for the PC/SC reader support.

The DisconnectStatus parameter tells the disconnect status when releasing the smart card.

The allow unlock mode is used to tell whether the PC/SC library should be unloaded or not when last connection is closed. Usually, unloading works quite bad if a later reconnect is wanted on some platforms.

The call trace mode may be activated to send information about each PC/SC call to the trace.

ModeCheckInfo gets information from the smart card reader driver. Unfortunately, there are reader drivers that will crash when they get asked, so it should normally be turned off.

ModeCheckInfoAllow is a whitelist of smart card readers for which to make information checks from the smart card reader driver. The information checks can for example be if the smart card reader is a PIN pad or not. Unfortunately, there are reader drivers that will crash when they get asked, so it should normally be turned off.

We recommend that you use either ModeCheckInfoAllow or ModeCheckInfoDeny.

ModeCheckInfoDeny is a blacklist of smart card readers for which to deny information checks from the smart card reader driver. The information checks can for example be if the smart card reader is a PIN pad or not.

We recommend that you use either ModeCheckInfoDeny or ModeCheckInfoAllow.

ModeCheckPinPad asks the smart card reader if PIN pad is supported or not. To use this function, ModeCheckInfoAllow or ModeCheckInfoDeny must be activated.

There are two modes when talking to PC/SC: either shared or exclusive. Using shared will allow other processes to connect simultaneously and should be considered to best behavior.

There are two modes for detecting smart card reader presence, either ask continuously or wait for a notification. The mode will be decided by the StateTimeout value, but this parameter may enforce the use of notifications even when asking continuously.

The normal behavior is to open a context towards PC/SC and close it when finished using, but there are implementations available that handles this bad, so we may continue to use the same context without closing it. This parameter is used when connecting towards a smart card.

The normal behavior is to open a context towards PC/SC and close it when finished using, but there are implementations available that handles this bad, so we may continue to use the same context without closing it. This parameter is used when scanning for smart card readers (list).

The normal behavior is to have a separate connection when scanning for smart card readers and another connection when connecting the smart cards. This parameter will reuse the same connection for both purposes.

There are two modes for detecting smart card reader presence, either ask continuously or wait for a notification. The mode will be decided by the StateTimeout value, but this parameter will stop the use of notifications even when using notifications for smart card presence.

The normal behavior is to release the smart card when finished working with it. This parameter will change the behavior to always connected. Not recommended when working with other processes that want to access the same smart card.

The normal behavior is expecting the smart card reader service to return the correct smart card presence status, but sometimes will unknown be returned. This parameter tells how unknown should be treated.

The normal behavior will be to allow multiple threads access the smart card reader service simultaneously as long as we are accessing different smart card readers. This parameter will block this behavior and require the other thread to be finished before accessing the second reader.

The scope tells the access scope.

If not specified, then will the client access with SCOPE_USER for normal user and SCOPE_SYSTEM for system user (root or administrator).

There are two modes for detecting smart card reader presence, either ask continuously or wait for a notification. Will ask continuously if this parameter is set to 0, and use notification if this value is non-zero. The value will be the number of minutes until timeout.

This variable tells whether the implementation should wait for the PC/SC smart card service to be started.