The usual pattern for RBAC is to test for the permission flags (and resource scope) that were acquired via your Role assignments, rather then directly testing for the Role itself.
Under "enterprise applications" I do not see my registered application, although I select "show all applications". o.Following the link from the app registration overview like you do in your video, I managed to see the Enterprise Application. But here it says: Groups are not available for assignment due to your Active Directory plan level. You can assign individual users to the application. I really liked your video but why not mentioning s.th. like this up front?
Thanks for the informative video. But why does none of this work for service accounts?
Thanks for your video's! Why not create roles and assign api scopes to a specific role? Is that possible? Then in my api i only have to check the scopes the user is granted for instead of checking the different role names.
Super useful video...but i am getting error on "AzureADDefaults" while configuring. Am i missing any library.
I don’t see roles in access token but I am seeing roles in id_token!! Strange why is that?
Thanks, informative video!
Very interesting thanks !
I see the code sample for general microsoft identity platform, where is the code he specifically uses?
@SimonPedersen1