You can also map the name of your claim to the name defined below. The InputClaims element contains a list of claims required to send to the one-time password protocol provider. Codes generated and attempts are tracked within the session. Below are the options that can be configured for this mode. The first mode of this technical profile is to generate a code. The following example shows a one-time password 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. With the validation technical profile, an error message is displayed on a self-asserted page. The validation technical profile validates the user-provided data before the user journey continues. A validation technical profile calls the one-time password technical profile to verify a code. Design the integration with the one-time password by using a Validation technical profile. The one-time password technical profile can also return an error message during code verification. Use a technical profile to generate a code, and then verify that code later.
#OTP CODE GENERATOR ONLINE VERIFICATION#
If you've not done so, learn about custom policy starter pack in Get started with custom policies in Active Directory B2C.Īzure Active Directory B2C (Azure AD B2C) provides support for managing the generation and verification of a one-time password. For most scenarios, we recommend that you use built-in user flows.
In Azure Active Directory B2C, custom policies are designed primarily to address complex scenarios.
0 kommentar(er)
