Unable to log in to Orchestrator Host hosted on AS.
Issue description:
- Upon attempting to log in, the user is repeatedly redirected to the login screen without successfully accessing the website.
- No specific error message is displayed, and the login process appears stuck in a loop.
Logs to collect:
- Network HAR logs
- Support Bundle as per the version
Root Cause:
If the HAR does not contain any errors and one is using Bookmarks the browser, the primary cause of this scenario could be using a bookmarked URL that includes a specific path (https://FQDN/somepath) rather than the base domain (https://FQDN). This specific path may:
- Bypass the standard authentication flow.
- Lead to an endpoint requiring prior authentication.
- Trigger a redirect loop, especially if the session handling for that path is misconfigured.
Detailed Analysis of Potential Failures:
- Incorrect Bookmark or Saved URL:
-
- Users may have saved a deep link (e.g., https://FQDN/somepath) instead of the base domain. Such links can skip initial session validation or point to restricted pages.
- Session Expiry or Invalid Session:
-
- If the session data for the bookmarked path is expired or invalid, the system might redirect to the login page but fail to establish a new session.
- Misconfigured Application Paths:
-
- Certain application paths may require additional parameters or preconditions that are not met when directly accessed through a bookmark.
- Cache or Cookie Issues:
-
- Browser cache or stale cookies can interfere with the login flow, causing unexpected behavior.
Resolution:
1. Update Bookmark or Saved URL:
- Always bookmark the base domain of the website (e.g., https://FQDN).
- Steps:
-
- Open the browser and navigate directly to the base domain (https://FQDN).
- Log in using valid credentials.
- Save the base domain as a new bookmark.
2. Clear Browser Cache and Cookies:
- Clearing cached data can help resolve issues caused by stale session cookies or cached redirects.
- Steps:
-
- Open browser settings.
- Navigate to "Privacy & Security."
- Clear cache and cookies.
- Restart the browser and try logging in again.
3. Verify Session and Authentication Flow:
- Ensure that the login is being initiated from the standard authentication page. Avoid accessing deep links before completing the login process.
- Steps:
-
- Open the base domain in an incognito/private browsing window.
- Log in to verify the correct flow.