PingOne MFA attributes reference
PingOne MFA provides two attributes that can be useful in your PingFederate authentication policy.
pingone.mfa.status attribute
This attribute describes the status of the current multifactor authentication request.
| Value | Description | ||
|---|---|---|---|
|
Set when MFA is bypassed for any reason, such as when a user without any trusted devices signs on from the web and the system is configured to bypass authentication for users without a trusted device. |
||
|
This status is returned on successful SMS authentication from a web sign on flow. |
||
|
This status is returned on successful email authentication from a web sign on flow. |
||
|
This status is returned on successful voice authentication from a web sign on flow. |
||
|
This status is returned on successful SDK mobile app authentication from a web sign on flow. |
||
|
This status is returned on successful biometric/security key authentication from a web sign on flow. |
||
|
This status is returned on successful WhatsApp authentication from a web sign on flow. |
||
|
This status is returned on successful third-party "timed one-time passcode" (TOTP) authenticator authentication from a web sign on flow. |
||
|
This status is returned on successful OATH token authentication from a web sign on flow. |
||
|
This status is returned on successful SMS authentication when the user signs on from an untrusted mobile device. |
||
|
This status is returned when a user signs on with an untrusted mobile device and is authenticated using their trusted email device. |
||
|
This status is returned on successful voice authentication when the user signs on from an untrusted mobile device. |
||
|
This status is returned on successful mobile authentication when the user signs on from an untrusted mobile device. |
||
|
This status is returned when a user signs on with an untrusted mobile device and is authenticated using their trusted third-party OTP authenticator. |
||
|
This status is returned on successful OATH token authentication when the user signs on from an untrusted mobile device. |
||
|
This status is returned on successful biometric/security key authentication when the user signs on from an untrusted mobile device. |
||
|
This status is returned when a user signs on from an untrusted mobile device and completes authentication with an authentication code. |
||
|
This status is returned on successful WhatsApp authentication when the user signs on from an untrusted mobile device. |
||
|
A user signs on when the system is configured to bypass authentication if there are network problems or PingOne is unreachable. |
||
|
Set when the end-to-end pairing process is completed. That is, the ID token from PingOne has been consumed by the PingOne mobile SDK and the user approved the pairing. |
||
|
Set when the device is paired through the front channel. The device is reported as not paired because the ID token is returned as part of the attribute contract and cannot be passed to the PingOne mobile SDK until after authentication. Also set as part of the API flow when the device was not paired. That is, the user was denied. |
||
|
Set when there is an error during the pairing flow. |
||
|
A user with no authentication methods was prompted to set up MFA, but they clicked Skip. |
||
|
This status is returned on successful PingID Mobile App authentication from a web sign-on flow. |
||
|
This status is returned on successful PingID Desktop App (Legacy) authentication from a web sign-on flow. |
||
|
This status is returned on successful PingID Desktop App authentication from a web sign-on flow. |
||
|
This status is returned on successful YubiKey authentication from a web sign-on flow. |
||
|
This status is returned on successful PingID Mobile App authentication when the user signs on from an untrusted mobile device. |
||
|
This status is returned on successful PingID Desktop App (Legacy) authentication when the user signs on from an untrusted mobile device. |
||
|
This status is returned on successful PingID Desktop App authentication when the user signs on from an untrusted mobile device. |
||
|
This status is returned on successful YubiKey authentication when the user signs on from an untrusted mobile device. |
||
|
This status is returned when authentication completes successfully using device authorization on a previously paired, trusted mobile device. Applies regardless of whether extra verification is required. If extra verification is enabled, the status is only returned after verification is successfully confirmed. |
||
|
This status is returned when device authorization succeeds on a trusted mobile device where:
|
||
|
MFA is bypassed because the user was not found in PingOne and the User Not Found Failure Mode is set to bypass authentication. |
||
|
MFA is bypassed because MFA is disabled for the user in PingOne. |
||
|
MFA is bypassed because the user authenticated using a client-side authenticator (such as Conditional UI, or passwordless sign-on). |
||
|
MFA is bypassed because the user does not meet the conditions that require MFA, such as IP range, user population, or user attributes defined in the adapter configuration. |
||
|
MFA was completed by an adapter other than the PingOne MFA IdP Adapter, such as an adapter for an external MFA provider. |
||
|
This status is returned when PingOne MFA reports that the MFA attempt failed. |
||
|
This status is returned when a policy denies authentication before the MFA attempt begins. |
pingone.mfa.status.reason attribute
When the pingone.mfa.status attribute is device_paired, this attribute describes the paired device. When the status is mfa_bypassed, this attribute is set to conditions_not_met.
| Value | Description |
|---|---|
|
The user is using SMS to authenticate. |
|
The user is using email to authenticate. |
|
The user is using a voice call to authenticate. |
|
The user is using the mobile app to authenticate. |
|
The user is using a third-party OTP authenticator to authenticate. |
|
The user is using an OATH token to authenticate. |
|
The user is using a biometric/security key authenticator to authenticate. |
|
The user is using WhatsApp to authenticate. |
|
The user is using the PingID Mobile App to authenticate. |
|
The user is using the PingID Desktop App (Legacy) to authenticate. |
|
The user is using the PingID Desktop App to authenticate. |
|
The user is using a YubiKey to authenticate. |
|
The user does not meet the conditions that require MFA, so MFA is bypassed and authentication succeeds. |
pingone.mfa.device.paired.type attribute
Indicates the authentication method that the user paired during the current authentication session.
| Value | Description |
|---|---|
|
Email authentication. |
|
SMS authentication. |
|
Voice authentication. |
|
WhatsApp authentication. |
|
Mobile app authentication. |
|
TOTP authenticator authentication. |
|
Platform authenticator authentication. |
|
Security key authentication. |
|
FIDO2 authenticator authentication. |
|
OATH token authentication. |
|
PingID Desktop authentication. |
|
PingID Desktop (Gen2) authentication. |
|
PingID Mobile authentication. |
|
YubiKey authentication. |
Passwordless authentication attributes
When the PingOne MFA IdP Adapter completes a passwordless (usernameless) authentication, it populates the following attributes in the PingFederate attribute contract. These attributes are available for use in downstream policy steps.
|
The |
| Attribute | Value | Description |
|---|---|---|
|
String |
The username resolved during passwordless authentication. |
|
|
Indicates whether passwordless authentication succeeded. |
|
|
The type of device used for passwordless authentication. |
|
String |
The unique identifier of the device used for passwordless authentication, as assigned by PingOne. |
|
String |
The PingID Desktop App version on the device that completed authentication, as defined in PingOne. Only populated when |
|
String |
The operating system version on the device that completed authentication, as defined in PingOne. Only populated when |