PingOne MFA status 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 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 third-party "timed one-time passcode" (TOTP) authenticator 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 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 biometric/security key 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. |
pingone.mfa.status.reason
attribute
When the pingone.mfa.status
attribute is device_paired
, this attribute describes the paired device.
Value | Description |
---|---|
|
The user is using SMS to authenticate. |
|
The user is using email 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 a biometric/security key authenticator to authenticate. |
|