You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you move the ClaimsProvider from the BuildingBlocks element to the sibling ClaimsProviders element , the policy is uploaded without errors.
You must make sure ClaimTypeReferenceId="signInNames.emailAddress" matches the ClaimType defined in the Base (in my case and probably others, this is email)
We apologize for the delay in our response. We'll investigate this custom policy, then update our docs accordingly. For now, we'll close this issue, then track it internally. #please-close.
Technology: Azure B2C Identity Experience Framework
Article: https://learn.microsoft.com/en-us/azure/active-directory-b2c/userinfo-endpoint?pivots=b2c-custom-policy
Description of the problem
1 - Article instructs user to place technical profile under the wrong XML element.
2 -
ClaimTypeReferenceId
is incorrecthttps://learn.microsoft.com/en-us/azure/active-directory-b2c/userinfo-endpoint?pivots=b2c-custom-policy#1-add-the-token-issuer-technical-profile
Step 1 "Add the Token Issuer technical profile" instructs you to add the
ClaimsProvider
info under theBuildingBlocks
element.However, if you do that, the policy will fail validation upon upload with error:
Solution:
If you move the
ClaimsProvider
from theBuildingBlocks
element to the siblingClaimsProviders
element , the policy is uploaded without errors.You must make sure
ClaimTypeReferenceId="signInNames.emailAddress"
matches the ClaimType defined in the Base (in my case and probably others, this isemail
)must be
Issue opened on the Azure-Samples repo before this one:
Azure-Samples/active-directory-b2c-custom-policy-starterpack#150
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: