You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 23, 2025. It is now read-only.
We have resolve this issue by creating a new enterprise application in Azure Entra, and configure basic SAML from the ground up. It turns out that the issue was due to our existing enterprise application was configured completely different from the guide. It was configured with openid connect and oauth as oppose to basic SAML from the guide instruction. We had the Identifier (Entity ID) set to the Application ID, whereas the SAML settings expects it to be same with callback URL.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem:
Persistent - Invalid_response error on login
Environment details:
Additional Info:
The text was updated successfully, but these errors were encountered: