Hi folks,

Firstofall, thanks for the amazing lib. I find it clean and efficient. 🤩

Documentation is great too, and I could setup the basics in Azure thanks to the explicit tutorial. Thanks a lot !

I wanted to go further, and I was looking for setting up user rights through BOOLEAN_CLAIM_MAPPING, and I am hitting the Azure wall of a-kilometer-high documentation.

Hence my question : could you add a section in the doc that describes the steps...

1. to declare and set the attribute user_is_staff and user_is_superuser in Azure
2. add the claims in the token
3. (and get them, but it looks like this part is already working fine :)

🧭 Status Point

Here are my findings of the last 24 hours trying to make it work on my own (being completely newbie with Azure)

I started from the settings reference in the project doc, about BOOLEAN_CLAIM_MAPPING

You can find the short name for the claims you configure in the ADFS management console underneath ADFS ➜ Service ➜ Claim Descriptions

I did not find such section in the Azure AD I created, neither in the Azure AD B2C :(

📔 Regarding AD:

The posts I have found redirect to the token configuration page, showing how to add optional claims, but only existing ones apparently...

Therefore I searched how to define my claims, i.e. my new attributes on the users, but I only found an azure feature custom security attribute which require a license and is still in PREVIEW.

It appears I am not on the good track

📚 Therefre I looked at AD B2C:

There, it looks simple to adjust the user attribute configuration (only availalbe on AD B2C though)

But... there is no "token configuration" page as mentioned in a lot of places. I found the reason in the Microsoft doc

The UI option Token configuration blade is not available for apps registered in an Azure AD B2C tenant which can be configured by modifying the application manifest. For more information see Add claims and customize user input using custom policies in Azure Active Directory B2C

Regarding the claims token configuration, it appears that I have to use user flows or policies (https://docs.microsoft.com/en-us/azure/active-directory-b2c/configure-tokens?pivots=b2c-user-flow)

But that did not look like the way to go either

🕵️‍♂️ Conclusion:

I am pretty sure I am just getting lost in Azure labyrithn and missing an obvious configuration.

Hence the my issue, and the suggestion about extending the Tutorial :)

If this process sounds trivial or is well-known to anyone, I am glad for any help

Cheers,
Emmanuel