Custom claims are not provided to the /.auth/me endpoint. - When using third party authentication, Microsoft AzureB2C
- Dominant language
- No language data
- Stars
- 346
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
Custom claims are not provided to the /.auth/me endpoint from Azure B2C when connected as a OpenID authentication
A clear and concise description of what the bug is.
If you add a custom attribute to the user attributes in the user flow, then populate that attribute.
( Which can be done using the graph api users endpoint and patching with the body extension_{clientid}_{attribute_name} // note all dashes need to be removed from the client id, where client id is from the application that stores user profile data. You can then use the graph beta api to pull in all attributes and validate the new custom attribute on the claims is there and populated https://docs.microsoft.com/en-us/answers/questions/655788/custom-user-attributes.html )
that attribute is not provided on the /.auth/me endpoint
**Expected behavior**
I would expect all populated claims from the B2C user as well as populated custom claims to be provided in the claims array on the /.auth/me endpoint
**Additional context**
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.