Reputation: 171
This question is similar to
But the situation is a little different:
Is any way to avoid this behavior? Maybe add some query?
Thanks!
Upvotes: 2
Views: 4349
Reputation: 7728
This is almost always related to a discrepancy between the app registration + app settings in the portal and what you have in your code.
Your application ID in the portal needs to match the client ID in your code, the sign-on URL needs to be the homepage URL starting with HTTPS and needs to match the configuration, reply url/redirectURI need to match, and the app needs to be registered under the right tenant that also matches what you have in your config.
If all of your settings and permissions are correct then you really should not receive this error.
Upvotes: 1