Hey Aayushi,
I believe you have configured wrong idenitier id, it needs to be your QA server url. But changing it from there will remove SSO from your localhost, so to avoid it create one more app registration in your entra id and then configure that for your QA server.
Also you need to only add one url in identifier id - https://app-name/SSO/. I don't think you need to add every url of your page or deeplink urls.
Thanks & Regards,
Naman Khard
Hello Aayushi,
i am facing the same issue and have no idea:
Connector: 404 - file not found for file: SubmitLoginForm
Could you solve the problem?
Thank you in advance.
Markus
It sounds like you're facing an issue where Single Sign-On (SSO) redirection is either failing or looping endlessly in your application. To help you better, here are some common causes and troubleshooting steps to diagnose and fix the issue:
Basic Questions
To narrow it down, please consider:
What SSO provider are you using? (e.g., Azure AD, Okta, Google, Auth0, etc.)
Is this a web app or mobile app?
What language/framework is the app built in?
Is the SSO initiated by the app (SP-initiated) or the identity provider (IdP-initiated)?
Do you get an error, or is it just stuck in a loop?
Common Problems & Fixes
1. Redirection Loop
Check if the application is unable to set the session or token after successful login.
Fix: Make sure your app sets a cookie or token after login and doesn't redirect back to the SSO page.
Ensure the callback URL is correct and whitelisted in the IdP.
2. Mismatched Redirect URI
If the redirect URI in your app doesn’t match the one configured in the IdP, the login will fail or loop.
Fix: Double-check the redirect URI settings on both app and IdP side.
3. Clock Skew
If your server and the IdP have different system times, SAML or token-based logins may fail.
Fix: Sync your server time (e.g., with NTP).
4. Missing or Invalid SSO Configuration
Check if the SSO metadata (SAML or OIDC) is correctly configured.
Confirm that the correct client ID, secret, and endpoints are used.
5. Incorrect Response Handling
Sometimes the app receives the SAML/ID token but fails to parse or validate it.
Fix: Check logs to see if the token is received and valid.
6. Third-Party Cookies Blocked
Some browsers block third-party cookies, which SSO might need to work.
Fix: Test on another browser or device to confirm this.
What You Can Do Now
Please share:
The error message or browser behavior (screenshot or console log if possible).
The SSO provider.
The framework (React, Angular, Django, etc.).
The callback/redirect URL you're using.
That will help me give you a more specific fix.
Would you like to share the SSO logs or the code snippet handling the redirection?