New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No longer obtaining email claim #16566
Comments
|
@mada360 |
|
Hi @mada360 , |
|
Closing this out for now but I'll be happy to keep track of this issue in the comments and ensure that your question gets resolved. |
|
@mada360 were you able to resolve this? |
|
I've just resolved this problem by adding OutputClaim ClaimTypeReferenceId="email" PartnerClaimType="unique_name" to OutputClaims of the ClaimProvider instead of OutputClaim ClaimTypeReferenceId="email" . |
|
Having the same issue. No email claim in token on multi tenant. I have also raised a case with Azure support. It's definitely a bug or problem. |
|
Is there a resolution for this |
|
I've wasted days on this. Why is it so difficult to get the email in our id_token claims is beyond me ! This is my <TechnicalProfile Id="PolicyProfile">
<DisplayName>PolicyProfile</DisplayName>
<Protocol Name="OpenIdConnect" />
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="givenName" />
<OutputClaim ClaimTypeReferenceId="surname" />
<OutputClaim ClaimTypeReferenceId="email" PartnerClaimType="email"/>
<OutputClaim ClaimTypeReferenceId="objectId" PartnerClaimType="sub"/>
<OutputClaim ClaimTypeReferenceId="tenantId" AlwaysUseDefaultValue="true" DefaultValue="{Policy:TenantObjectId}" />
</OutputClaims>
<SubjectNamingInfo ClaimType="sub" />
</TechnicalProfile>Thank you! |
|
@iliassk I'm not on the microsoft team but I can try to help. When you inspect the token on jwt.ms do you see the claims there after signin? My first thought is that you need to also include If you're seeing it in the token on jwt.ms but its not in the claims when you examine the token in your backend application, make sure you have an SSO reflector that ensures the claim is maintained in an SSO session |
|
Hey @CodyMorris! Thank you. I managed to find a solution by using this instead: <OutputClaim ClaimTypeReferenceId="signInName" PartnerClaimType="email"/>I don't get why it is so difficult to retrieve the email claim from the And I just found out that we can't get RBAC or retrieve user roles neither in the token: https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/10123836-get-user-membership-groups-in-the-claims-with-ad-b |
|
@iliassk for getting group claims from AzureAD, we use the Graph API in our actual application. For other idP's we return it in a custom attribute and ingest it with B2C IEF. And yes, its a nightmare and i'm not sure why |
|
Also amazed at this and the fact the issue was closed! Our application allows users to plug in any OpenID Connect provider yet it was not working with Azure B2C, and this is the reason. The @MarileeTurscak-MSFT this is a bug. Fix it please Microsoft. |
|
Is anyone also having the same problem but with Azure AD B2C? in my case the email is not returned. |
|
Yes, right now it seems the only workaround is to use a custom policy to export |
Previously I had implemented these custom policies to allow for multi-tenant sign on and I was able to obtain the email address for the user but since the move to using the b2clogin domain I am now unable to obtain the email address in the token returned and there is no record of the email address against the user when looking at the user dashboard within the Azure AD B2C blade.
Another difference is that the username for a multi-tenant user used to reflect the sts.windows.net/ as the username, I feel this has now been moved to the source associated with the user, but I'm wondering if this is related to the same issue as above.
With the move to the b2clogin domain, is it now expected that a seperate call be made to microsoft graph to obtain the extra details for the user? If so, is it possible to map the email of a user to be returned as a claim within the token.
Within my trial and error, I have also allowed for full permissions for the Azure AD B2C App to ensure that the email claim had not become more protected as I undestand that the B2C environment is constantly changing .
Thanks for any help with this issue.
Document Details
The text was updated successfully, but these errors were encountered: