Configuring security key authentication - PingID

PingID Administration Guide
bundle
pingid
ft:publication_title
PingID Administration Guide
Product_Version_ce
PingID
category
ContentType
Product
Productdocumentation
pingid
ContentType_ce
Product documentation

Use the FIDO2 security key for web-based authentication only. The browser with which the user is accessing their resources must support WebAuthn, such as the latest version of Google Chrome or Mozilla Firefox.

Note:

Define the use of security keys for offline authentication when installing the PingID Integration for Windows Login.

Important:

If the browser does not support WebAuthn, the user will be unable to authenticate with the security key and might be unable to authenticate if that is their only authenticating device.

  1. Sign on to the admin console.
  2. Go to Setup > PingID > Configuration.
  3. Go to the Alternate Authentication Methods section, and in the Security Key row, select the Enable check box.
    A screen capture of the Alternate Authentication Methods section.
    The ability to pair and authenticate with a security key is enabled for all users in that organization, and additional security key configuration fields are shown.

    mage showing Resident Key and User Verification configuration options for use with a security key.

  4. In the Enable column, select the Security Key check box.
  5. Optional: In the Security Key section, configure the following fields:
    • Resident Key. When set to Required, the private key is saved on the security key. To enforce passwordless authentication on all authentication attempts, set this field to Required.
    • User Verification. This option requires the user to perform a gesture using their security key, to validate their identity (for example, using their fingerprint, or entering a PIN code). Select either:
    • Required: only security keys that support user verification can be used to authenticate. When the Resident Key field is set to Required, this option is automatically set to Required.
    • Preferred (default): user verification is performed if the user's security key supports it, and is skipped if not supported.
    • Discouraged: user verification is not performed, even when supported by the user's security key. In cases where user verification is required by the security key itself, this setting does not override the device setting.
    CAUTION: When user verification is changed from preferred to required, it will automatically unpair all security keys that have not undergone user verification during registration or authentication in the past. To identify security keys that have not been registered as security keys that support user verification, see the fidoUserVerification field in the PingID User Detailed Status Report fields.
    Note: To enable passwordless authentication with a security key, you also need to create a PingFederate policy for passwordless authentication with a security key.
  6. To enforce the PingOne FIDO policy during authentication and registration, select the Enforce PingOne FIDO Policy check box.
    Note:
    • This feature is only available for organizations that are using a PingID environment that is integrated with PingOne or created by PingOne.
    • Only the default PingOne FIDO policy is enforced. To edit the policy or change the default policy, see Managing FIDO policies.
  7. Click Save.
Users can pair and authenticate with their security keys.