Reputation: 33
I have an employee who gets this error. However this is only on her own PC - If she changes to another PC she can log in and it works so I guess it's machine-wise, anyone got some suggestions?
Upvotes: 1
Views: 4494
Reputation: 33
As you see here the URL is exactly the same
[![enter image description here][2]][2]
Upvotes: 0
Reputation: 28
I had the same problem recently. Like your situation, I have exactly the same URL in my application and in Azure AD, but still have the "AADSTS50011 error".
Finally, this error message is nonsense. I add the following configuration to allow the Azure Application to read all types of user groupe and resolved the problem. (Azure AD application > Token Configuration > add groupes claim):
Upvotes: 1
Reputation: 9519
To deal with this kind of problem, you can try a general solution:
When you visit the application url , you will be redirected to the login page. Decode the authorization request url, you will find redirect_url
, copy the value of redirect_url
and paste it into the azure portal, and try again.
For the redirect URL, it should start with https
, if you need to start with http
, you must configure it as http://localhost
.
Upvotes: 0