由于这些自定义策略很难调试，所以我很小心地使用了现有的策略并添加了我的策略

<TechnicalProfile Id="LocalAccountSignUpWithReadOnlyEmail">
<DisplayName>Email signup</DisplayName>
<Protocol Name="Proprietary" Handler="Web.TPEngine.Providers.SelfAssertedAttributeProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null"/>
<Metadata>
    <Item Key="IpAddressClaimReferenceId">IpAddress</Item>
    <Item Key="ContentDefinitionReferenceId">api.localaccountsignup</Item>
    <Item Key="language.button_continue">Create</Item>
</Metadata>
<CryptographicKeys>
    <Key Id="issuer_secret" StorageReferenceId="B2C_1A_TokenSigningKeyContainer"/>
</CryptographicKeys>
<InputClaimsTransformations>
    <!-- Copy the InvitationId to CopyInvitationId claim type-->
    <InputClaimsTransformation ReferenceId="CopyInvitationId"/>
</InputClaimsTransformations>
<InputClaims>
    <InputClaim ClaimTypeReferenceId="email"/>
    <InputClaim ClaimTypeReferenceId="ReadOnlyInvitationId"/>
    <InputClaim ClaimTypeReferenceId="displayName" PartnerClaimType="displayName"/>
</InputClaims>
<OutputClaims>
    <OutputClaim ClaimTypeReferenceId="objectId"/>
    <OutputClaim ClaimTypeReferenceId="email" PartnerClaimType="Verified.Email" Required="true"/>
    <OutputClaim ClaimTypeReferenceId="newPassword" Required="true"/>
    <OutputClaim ClaimTypeReferenceId="reenterPassword" Required="true"/>
    <OutputClaim ClaimTypeReferenceId="executed-SelfAsserted-Input" DefaultValue="true"/>
    <OutputClaim ClaimTypeReferenceId="authenticationSource"/>
    <OutputClaim ClaimTypeReferenceId="newUser"/>
    <!-- Optional claims, to be collected from the user -->
    <OutputClaim ClaimTypeReferenceId="displayName"/>       
</OutputClaims>
<ValidationTechnicalProfiles>
    <ValidationTechnicalProfile ReferenceId="AAD-UserWriteUsingLogonEmail"/>
</ValidationTechnicalProfiles>
<UseTechnicalProfileForSessionManagement ReferenceId="SM-AAD"/>

因此，我有一个自定义的属性来自一个令牌提示以及其他电子邮件，显示名称一样的属性了。