A personal Gmail account redirects to Okta when residual Single Sign-On (SSO) session data or device account settings from a prior work configuration remain active in the browser or on the device. Personal Gmail accounts do not natively redirect to Okta unless they are tied to an SSO integration. Clearing stored session data, removing old work accounts from the device, or using a separate browser resolves the redirect.

The following symptom may occur:

• Navigating to Gmail redirects the browser through an Okta login page instead of the standard Google sign-in page.

• Okta Classic Engine
• Okta Identity Engine (OIE)
• Single Sign-On (SSO)
• Google Workspace SSO integration
• Personal Gmail accounts affected by residual work SSO configuration

Okta redirects occur when a browser or device retains session cookies, cached credentials, or account configurations from a prior work or school Google Workspace SSO setup that used Okta. Personal Gmail accounts do not redirect to Okta by default. The redirect is caused by one or more of the following residual configurations:

• Stored Okta and Google session cookies in the browser.
• A work account with Okta SSO was previously added to the device or a mail application.
• An active Okta session persists in the browser or at the system authentication layer.

How Is a Personal Gmail Redirect to Okta Resolved?

The following steps address the most common causes of a personal Gmail account redirecting to Okta. Complete each step in order and test Gmail access after each one.

1. Clear stored Okta and Google cookies and cached data from the browser. This removes the saved redirect session. The following steps describe how to clear browsing data:

   1. Navigate to the browser's Settings menu.

   2. Go to Privacy and Security.

   3. Select Clear browsing data.

   4. Select cookies, cached images, and files.

   5. Restart the browser, then try signing in to Gmail again.

2. Open Gmail in a private or incognito browser window. This avoids stored cookies and extensions that may trigger the Okta redirect. If Gmail loads correctly in a private window, the issue is related to the browser cache or session data.

3. Try a different browser. Switching to a different browser (for example, a browser other than the one currently in use) can prevent Okta redirects when accessing Gmail. This is especially relevant on mobile devices or devices where default login services interfere with the sign-in flow. Use a browser that best fits organizational guidelines. 

4. Remove old work accounts and SSO sessions from the device. If a work account with Okta SSO was previously added to the device, remove it from the following locations to stop the device from automatically redirecting through Okta:

   • Device account settings

   • Mail applications

   • Google applications on the device

5. On mobile devices, authentication redirect flows can persist even after removing accounts because applications may use an embedded browser or system authentication session. Clear website data in the device settings or remove and reinstall the affected application.

NOTE: If the redirect persists after completing all steps, review the Google account's connected applications and SSO configurations in the Google account security settings for any remaining work-related integrations.

Related References

• Google Workspace