30.9 Biometrics page (Operation Settings)
Setting |
|
Default value |
Yes |
Description |
When this option is set, if you have skipped any fingerprints and not reached the minimum number of fingerprints as specified in the Enforce a minimum number of fingerprints during enrollment? configuration option, you must provide a reason for not capturing the minimum number of fingerprints in the Confirm Finger Capture dialog. Note: The Account for missing fingerprints and Enforce a minimum number of fingerprints during enrollment? options are not enforced when capturing fingerprints using the MyID Operator Client. |
Further information |
See your biometric integration guide for details. |
Setting |
|
Default value |
No |
Description |
Allows the Preface control to capture non-compliant images. |
Further information |
For information on using Aware PreFace, contact customer support, quoting reference SUP-228. |
Setting |
|
Default value |
Yes |
Description |
Allows the user to log on with biometrics to complete a PIN reset. |
Further information |
See the Self-service PIN reset authentication section in the Operator's Guide. |
Setting |
|
Default value |
CROSSMATCH_GUARDIAN |
Description |
When the Fingerprint enrollment device option is set to Handprint capture, this option contains a comma-separated list of fingerprint devices that can be used by the Aware Fingerprint Capture component. If the Fingerprint enrollment device option is set to anything other than Handprint capture, this option is ignored. If you leave this option blank, the default behavior is to use Crossmatch Guardian devices. |
Further information |
See the Aware Fingerprint Capture guide provided with the Aware Fingerprint Capture module. For information on this module, contact your account manager. |
Setting |
|
Default value |
|
Description |
Aware custom profile. |
Further information |
For information on using Aware PreFace, contact customer support, quoting reference SUP-228. |
Setting |
|
Default value |
|
Description |
Aware custom profile. |
Further information |
For information on using Aware PreFace, contact customer support, quoting reference SUP-228. |
Setting |
|
Default value |
|
Description |
Aware custom profile. |
Further information |
For information on using Aware PreFace, contact customer support, quoting reference SUP-228. |
Setting |
|
Default value |
Precise |
Description |
Select the biometric matching library to be used. |
Further information |
See the integration guide for your fingerprint readers. |
Setting |
|
Default value |
50 |
Description |
Threshold of confidence of matching prints, 0-100. |
Further information |
See the integration guide for your fingerprint readers. |
Setting |
|
Default value |
10000 |
Description |
Setting for Precise biometric readers. Must be in the range 250 to 2,500,000. |
Further information |
Precise biometric readers are no longer supported in MyID |
Setting |
|
Default value |
10000 |
Description |
The BioSensitivity value refers to the failure rate of mismatches for U.are.U biometric readers. Must be in the range 250 to 2,500,000. |
Further information |
See the U.are.U Integration Guide for details. |
Setting |
|
Default value |
No |
Description |
Determines whether MyID generates an EFT from the biometrics when capturing fingerprints. |
Further information |
This feature is used in conjunction with the optional OPM Adjudication or EFT Export modules. Without these modules installed, MyID generates and stores the EFT from the biometric data captured, but you must install the relevant module to send the EFT to OPM for adjudication or to export the EFT files. |
Setting |
|
Default value |
No |
Description |
Determines whether MyID captures fingerprint rolls in addition to individual fingerprints when capturing fingerprints. |
Further information |
|
Setting |
|
Default value |
60 |
Description |
Threshold of acceptable of a captured fingerprint image. For PIV, a minimum of 60 is required, which maps to an NFIQ value of 3. Valid values are 20, 40, 60, 80, and 100, which map to NFIQ values 5, 4, 3, 2, and 1. |
Further information |
See the U.are.U Integration Guide for details. |
Setting |
|
Default value |
Yes |
Description |
Determines whether MyID captures fingerprint rolls in addition to individual fingerprints when capturing fingerprints for EFT capture. You must also have the Capture EFT Biometric Samples configuration option set, or MyID will not capture fingerprint rolls. |
Further information |
This feature is used in conjunction with the optional OPM Adjudication or EFT Export modules. |
Setting |
|
Default value |
Yes |
Description |
Allows the configuration of additional options in the Credential Profiles workflow. |
Further information |
See section 11.3.2, Additional credential profile options for details. |
Setting |
|
Default value |
No |
Description |
Whether biometric facial capture is enabled for MyID. Also controls the import of facial biometrics through the MyID Core API. |
Further information |
For details of capturing facial biometrics in MyID, see the Capturing facial biometrics section in the MyID Operator Client guide. For details of importing facial biometrics, see the API documentation provided with the MyID Core API. |
Setting |
|
Default value |
2 |
Description |
When the Account for missing fingerprints option is set, if you have skipped any fingerprints and not reached the minimum number of fingerprints as specified in this option, you must provide a reason for not capturing the minimum number of fingerprints in the Confirm Finger Capture dialog. Note: The Account for missing fingerprints and Enforce a minimum number of fingerprints during enrollment? options are not enforced when capturing fingerprints using the MyID Operator Client. |
Further information |
See your biometric integration guide for details. |
Setting |
|
Default value |
Yes |
Description |
Enforces the Require Fingerprints at Issuance and Require Facial Biometrics options in the credential profile so that fingerprints and facial biometrics are always required when requesting a device. The Require Fingerprints at Issuance and Require Facial Biometrics options are enforced at issuance, but this option makes sure that a request cannot be created, thereby catching the issue with the person's biometrics at an earlier stage. Note: This affects requests made using the MyID Operator Client only. |
Further information |
Setting |
|
Default value |
Precise 250 MC |
Description |
Which fingerprint reader to use. If you set this option to Handprint capture, you must also use the Aware Fingerprint Component supported devices option to specify which 10-slap scanners are to be used. |
Further information |
See the integration guide for your fingerprint readers. For information on 10-slap scanners, see the Aware Fingerprint Capture guide provided with the Aware Fingerprint Capture module. For information on this module, contact your account manager. Note: In versions of MyID earlier than MyID 12.10, this setting was named Crossmatch Guardian instead of Handprint capture. |
Setting |
|
Default value |
Yes |
Description |
Determines whether fingerprints are stored as live or pending when captured. Pending fingerprints become live only after the person has successfully completed their identity verification checks. Set this value to Yes to flag captured fingerprints as pending until the identity check has verified that they are valid. Set this value to No to make fingerprints live and available for use as soon as they are captured. |
Further information |
Available only when the Adjudication module is installed. See the Adjudication Integration Guide provided with the Adjudication module for details. |
Setting |
|
Default value |
|
Description |
Number of attempts the cardholder can make when attempting to validate fingerprints. If this value is blank, the default is 3. |
Further information |
See the Authenticating a person section in the MyID Operator Client guide. |
Setting |
|
Default value |
Yes |
Description |
If set to Yes, fingerprint authentication is required to collect derived credentials. |
Further information |
See the Derived Credentials Configuration Guide for details. |
Setting |
|
Default value |
Yes |
Description |
When set to Yes, removes any biometric readers that are flagged for enrollment only from the list of available readers when performing a match in the Unlock Card and Activate Card workflows. |
Further information |
Set this option to No only if you are experiencing problems with the detection of biometric readers. This option is not relevant for biometric operations carried out using the MyID Operator Client. |
Setting |
|
Default value |
0 |
Description |
This setting controls the brightness for SecuGen fingerprint readers. Set to a value between 0 (dark) and 100 (bright) |
Further information |
See the SecuGen Integration Guide for details. |
Setting |
|
Default value |
50 |
Description |
This setting controls the capture quality for SecuGen fingerprint readers. Set to a value between 0 (low quality) and 100 (high quality) |
Further information |
See the SecuGen Integration Guide for details. |
Setting |
|
Default value |
Yes |
Description |
Controls when fingerprints are required. Setting this to Yes will enable biometric samples to be used to identify an individual when issuing a card. Requires a data model that writes fingerprints to the card. For example, the PIV data models are suitable, but the CIV data models are not. |
Further information |
See your fingerprint reader integration guide for details. |
Setting |
|
Default value |
Yes |
Description |
Controls when fingerprints are required. Setting this to Yes will enable biometric samples to be used to identify an individual when unlocking a card. |
Further information |
See your fingerprint reader integration guide for details. |
Setting |
|
Default value |
No |
Description |
Controls when fingerprints are required. Setting this to Yes will enable biometric samples to be used to identify an individual when updating a card. Also used in conjunction with the Verify Fingerprints During Card Update option in the Issuance Settings section of the credential profile to control whether fingerprints are requested in the Collect Updates workflow. See the Collect Updates workflow section in the Operator's Guide. |
Further information |
See your fingerprint reader integration guide for details. |