A cloud-based identity and access management service for securing user authentication and resource access
Azure Enterprise Application "Default Role" Assignment Bug?
I create in Azure an "App Registration" & "Enterprise Application (Service Principal)" e.g. "app01". Then I add a redirect URL e.g. "http://localhost" to the App Registration. And finally I login/sign-in using the "Microsoft identity platform and OAuth 2.0 authorization code flow" and calling
https://login.microsoftonline.com/${tenant}/oauth2/v2.0/authorize?response_type=code&redirect_uri=http%3A%2F%2Flocalhost&client_id=${appid01}&scope=openid+profile+email&response_mode=query
Then all of sudden without any information or warning (and some delay) a "Default Role" assignment is added to the "Enterprise Application (Service Principal)", tab "Users and groups".
I did not notice this assignment and activated "Assignment required" ("Enterprise Application (Service Principal)", tab "Properties"). I then closed all browsers and again tried to log-in/sign-in with the same user and still I could login even I had not assigned any roles to this user.
On the other hand if I first activate "Assignment required" before login for the first time then the user cannot login because no role has been assigned to this user.
I guess this is a bug. It is fine that a user without any roles assigned can login as long as the "Assignment required" flag is not set but once this flag has been set the user should not be able to login anymore without explicit role assignment.