-
Notifications
You must be signed in to change notification settings - Fork 599
Signup with different email than the email passed as id_token_hint #466
Unanswered
adnan-ashfaq
asked this question in
Q&A
Hi,
I am looking into the the same https://github.com/azure-ad-b2c/samples/tree/master/policies/invite. And was wondering that on step three after the user clicks the invite link, can a user siginup with different email than what is passed through id_token_hint (if the email field isn't read only),?
flow
All reactions
Replies: 1 comment
Have you looked at the profile or just the image? It seems to be using ReadOnlyEmail.
<ClaimsProviders> <ClaimsProvider> <DisplayName>Local Account</DisplayName> <TechnicalProfiles> <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> <-- .. --> </Metadata> <InputClaimsTransformations> <!--Sample: Copy the email to ReadOnlyEamil claim type--> <InputClaimsTransformation ReferenceId="CopyEmailAddress" /> </InputClaimsTransformations> <InputClaims> <!--Sample: Set input the ReadOnlyEmail claim type to prefilled the email address--> <InputClaim ClaimTypeReferenceId="ReadOnlyEmail" /> </InputClaims> <OutputClaims> <OutputClaim ClaimTypeReferenceId="objectId" /> <!-- Sample: Display the ReadOnlyEmail claim type (instead of email claim type)--> <OutputClaim ClaimTypeReferenceId="ReadOnlyEmail" Required="true" /> <OutputClaim ClaimTypeReferenceId="newPassword" Required="true" /> <OutputClaim ClaimTypeReferenceId="reenterPassword" Required="true" /> <-- .. --> </OutputClaims> <ValidationTechnicalProfiles> <ValidationTechnicalProfile ReferenceId="AAD-UserWriteUsingLogonEmail" /> </ValidationTechnicalProfiles> <UseTechnicalProfileForSessionManagement ReferenceId="SM-Noop" /> </TechnicalProfile> </TechnicalProfiles> </ClaimsProvider>
All reactions
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment