Open mitchflores opened 3 months ago
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.
Problem: Persistent - Invalid_response error on login
Environment details:
Additional Info: