<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language

Okta Prompts for Password After Successful OIDC IDP Federation

Okta Classic Engine
Okta Identity Engine
API Access Management

Overview

When an administrator federates an Okta tenant to a third-party Identity Provider (IdP) using OpenID Connect (OIDC), Okta generates an unexpected password challenge immediately after a successful OIDC authentication. This occurs because the ID token that the IdP issues lacks an Authentication Methods References (amr) claim, causing Okta to treat the sign-in as not satisfying any factors. Configure the IdP to include the amr claim in the ID token that it sends to Okta to resolve the issue.

Applies To

  • Okta Identity Engine (OIE)
  • Okta Classic Engine
  • OpenID Connect (OIDC)
  • Identity Provider(IdP) Federation

Cause

This error occurs when an administrator enables the Trust claims from this identity provider setting in Okta, but the ID token that the generic IdP issues does not contain an amr claim. Okta uses the amr claim in the ID token to determine which authenticators the user has already satisfied. Without this claim, Okta treats the IdP sign-in as not satisfying any factors, which prompts the authentication policy to require the password authenticator.

Solution

How is the password challenge resolved for a generic OIDC IdP?

Configure the generic OIDC IdP(for example, Entra or Google) to include the Authentication Methods References (amr) claims in the ID token.

When the amr claim is present, Okta maps the supported values to authenticators and evaluates them against the authentication policy rule to prevent the additional password prompt.

 

Related References

Loading
Okta Prompts for Password After Successful OIDC IDP Federation | Okta Support