问题描述
如何在具有自定义策略的B2C中启用电子邮件验证?
How do I enable email verification in B2C w/ custom policies?
为了进行反向工程,我尝试在内置策略中禁用它并下载了该策略.我尝试将该元数据项添加到我的自我声明的技术资料中,但这没用.
In an attempt to reverse engineer it, I tried disabling it in a built-in policy and downloaded the policy. I tried adding that metadata item to my self-asserted technical profile but that didn't work.
反向工程师测试|内置政策
<TechnicalProfile Id="SelfAsserted-Input">
<Metadata>
<Item Key="EnforceEmailVerification">False</Item>
</Metadata>
</TechnicalProfile>
我自行声明的技术资料
<TechnicalProfile Id="LocalAccountSignUp">
<DisplayName>User signup</DisplayName>
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.SelfAssertedAttributeProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
<Metadata>
<Item Key="EnforceEmailVerification">True</Item>
</Metadata>
...
</TechnicalProfile>
在重要的情况下,我正在为本地帐户使用用户名.
I'm using usernames for local accounts incase that matters.
推荐答案
是否使用基于电子邮件地址或基于用户名的登录名创建本地帐户,都可以通过添加 PartnerClaimType =添加电子邮件验证已验证您自己声明的技术资料的电子邮件"输出声明中的已验证.电子邮件"
,如下所示:
Whether a local account is created with an email address- or user name-based sign-in name, you add email verification by adding PartnerClaimType="Verified.Email"
to the "email" output claim of your self-asserted technical profile, as follows:
<OutputClaim ClaimTypeReferenceId="email" PartnerClaimType="Verified.Email" Required="true" />
这篇关于如何在Azure AD B2C中启用电子邮件验证的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!