Okta Classic Engine Authentication Endpoint Remains Active After Okta Identity Engine Upgrade

The /api/v1/authn endpoint remains active after an organization upgrades to Okta Identity Engine (OIE) to maintain backward compatibility with legacy applications. To resolve this issue and prevent scripted clients from calling the legacy endpoint, administrators must audit the environment and contact Okta Support to disable the endpoint at the organization level.
Users experiencing login errors might have bookmarked URLs that still use the legacy authentication flow.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Authentication API

Okta retains the /api/v1/authn core legacy endpoint strictly for backward compatibility with applications created on Okta Classic Engine that require migration to OIE. OIE uses a new dedicated authentication flow that relies on the /api/v1/idx endpoint. The legacy endpoint does not become unavailable automatically after the upgrade.

What steps are required to disable the legacy authentication endpoint?

Contact Okta Support to disable it by following these steps.

1. Audit the organization to confirm no legitimate clients still use the /api/v1/authn endpoint.
2. Open a case with the Okta Support team to request the deactivation of the /api/v1/authn endpoint at the organization level.

Resolve User Login Errors Caused by Bookmarked URLs

Users experiencing login errors might have bookmarked URLs that still use the legacy authentication flow. Instruct users to update any bookmarked URLs and provide them with the correct URL.