The following options can be configured for this step. The verify code step verifies a code sent to the user. The following example shows an Azure AD MFA technical profile that is used to send a code via SMS. User error message if a request has been throttled. User error message if the server has encountered an internal error. User error message if the phone number provided is not a valid phone number. User error message if the phone number provided does not accept SMS. The metadata should be configured in the self-asserted technical profile. The following metadata can be used to configure the error messages displayed upon sending SMS failure. The Metadata element contains the following attribute. The Azure AD MFA protocol provider doesn't return any output claims, so there's no need to specify output claims. If not provided, the browser locale of the user is used. If not provided, the name of your application is used. The identifier for the user who owns the phone number. You can also map the name of your claim to the name defined in the MFA technical profile. The InputClaims element contains a list of claims to send to Azure AD MFA. To verify a phone, the first step generates a code and sends it to the phone number. The following screenshot shows the phone verifier flow. The technical profile provides methods to send the verification code via SMS text message, and verify the code. Validates a phone number via text messages.
Uses the Azure AD MFA service to generate and send a code to a phone number, and then verifies the code.Instead, the user interface is called from a self-asserted technical profile, or a display control as a validation technical profile. Doesn't provide an interface to interact with the user.With the validation technical profile, an error message displays on a self-asserted page. The validation technical profile validates the user-provided data before the user journey continues. The Azure AD MFA technical profile may also return an error message. In the verify phone mode, the technical profile generates and sends a code to a phone number, and then verifies the code. The following example shows an Azure AD MFA technical profile: The handler attribute must contain the fully qualified name of the protocol handler assembly that is used by Azure AD B2C:, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null The Name attribute of the Protocol element needs to be set to Proprietary. Azure Active Directory B2C (Azure AD B2C) provides support for verifying a phone number by using a verification code, or verifying a Time-based One-time Password (TOTP) code.
0 kommentar(er)
