MiniDriver

Our MiniDriver allows all certificates by default, but there are scenarios when some certificates should be ignored. The AllowCertificate parameter specifies the matching condition that should be fulfilled.

Our MiniDriver allows all smart cards by default, but there are scenarios when some tokens should be ignored. The AllowToken parameter specifies the matching condition, see Tokens for more information.

Our MiniDriver handles certificate compression, but the parameter can also disable the compression and let the caller handle it. We do not recommend to use this, since our MiniDriver need the real certificate value. But it can still be used during certification testing.

The ComponentEnable and ComponentDisable parameters allows the use of conditions to blacklist and/or whitelist an applications' use of the MiniDriver.

The CheckFileCMap parameter verifies the MiniDriver cmapfile towards the actual certificates/key pairs stored on the smart card at loading time.

The FileCacheDisable parameter disables the MiniDriver file cache.

The GuidKeyId parameter specifies whether smart card key identifier should be used as key identifier or if a GUID should be generated.

The IgnoreFileCardCF parameter disables cardcf written by caller, instead automatically generated.

The IgnoreFileCMap parameter disables cmapfile written by caller, instead automatically generated.

The IgnoreLogout parameter disables all attempts to logout a smart card by the caller, to avoid interference with single sign-on.

The MiniDriver handles key generation, but the KeyGeneration parameter is used to disable the key generation and let the caller handle it.

The MiniDriver reads actual supported key sizes from the smart card. Use these parameters to limit the values. The key sizes are in bits.

The MiniDriver generates cmapfile from certificate and key pairs on the smart card by default. The NoPkcs11Certificates parameter disables the loading of certificates.

The MiniDriver generates cmapfile from certificate and key pairs on the smart card by default. The NoPkcs11Keys parameter disables the loading of key pairs.

The MiniDriver can specify that the PIN should be cached or not, single sign-on provided by caller.

The MiniDriver may specify that the non-repudiation PIN should be cached or not, single sign-on provided by caller.

The MiniDriver can specify how long the PIN should be cached by caller. The value is in number of seconds, 0 for no timeout.

ProviderName is the name of the CSP that our certificate propagation service registers certificate to, that is Microsoft Base Smart Card Crypto Provider.

ProviderType is the type of CSP that our certificate propagation service registers certificate to, that is Microsoft Base Smart Card Crypto Provider.

The ReadOnly parameter disables all updating of the smart card via the MiniDriver interface.

The RegisterCardPrefix parameter sets the prefix to use when registering supported smart cards.

The ReplaceCertificate parameter specifies if an existing certificate (using same key ID) should be overwritten when a new certificate is written.

The certificate can be sorted before it is returned to the calling application. This allows some kind of default certificate control, but should probably not be used any longer since it only tells in what sequence the MiniDriver will return certificates. The intended function is to control the order of certificates for a certificate selection dialog, but there are too many layers of interfaces to predict the outcome. For example, the order can be updated by CryptoAPI or the certificate selection dialog.

The MiniDriver file cardcf is used as update counter, and some smart cards are using the same format for their smart cards. The UseExternCardCF parameter synchronizes those values.

The MiniDriver handles padding of data before signature, or after decryption. This parameter is used to disable the padding and let the caller handle it.

The MiniDriver supports version 4 to 7. The Version parameter limits the support to a lower number.

The MiniDriver generates a virtual file system to handle the files and directories created. To increase performance on some smart cards, it is recommended to allocate the virtual file system in blocks.