Okta Session/Me API Returns a "404 Not Found" Error
Last Updated:
Administration
Okta Classic Engine
Okta Identity Engine
Overview
Calling the following endpoint from a third-party website in Google Chrome fails when accessed through either the default domain or a custom domain:
https:// ${OktaDefaultDomain} /api/v1/sessions/me
https:// ${OktaCustomDomain} /api/v1/sessions/me
This occurs because the Google Chrome security settings for incognito mode block sites from leveraging browser cookies to track activity across different sites. Allowing third-party cookies in the Google Chrome privacy settings resolves this error. When this failure occurs, Okta returns the following error:
404 Not Found
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Google Chrome
- Cookies
- Third-party website
Cause
The Google Chrome security settings for incognito mode block sites from leveraging browser cookies to track activity across different sites.
Solution
What resolves the 404 Not Found error?
Allow third-party cookies in the Google Chrome settings and test the API endpoint.
- Navigate to the Google Chrome Settings.
- Select Privacy and Security from the left-hand side menu, and then select Third-party cookies.
- Select Allow third-party cookies.
- Sign in to the Okta organization and test the API in the browser using either the default domain or the custom domain.
