This article discusses the situation in which a 400 error is received while trying to authenticate with Okta using OpenID Connect (OIDC).

SCIM-enabled applications or a custom SCIM connector fail with a "No results for users returned" error visible in the Okta Admin Dashboard.

Applications use supported methods like Okta-hosted login, embedded widgets, or specific SDKs to authenticate with the Interaction Code Flow.

Pass a custom attribute in the OpenID Connect assertion and map it to the login attribute in the target Okta organization.

Understanding the differences between an OpenID Connect application session and an Okta session clarifies how they relate and how to end them.

Assign the Super Administrator role to the account making the API call to resolve the E0000006 error on the application grants endpoint.

Compute the Authorization Code hash value used in the Okta System Log by executing specific shell commands on the raw Authorization Code value.

Add a new API access policy or update the issuer URI to resolve an Okta sign-in error caused by a missing default custom authorization server policy.

Accept the new Apple agreements and re-authenticate the SCIM integration to resolve daily directory sync failures.

Consult Azure Support to resolve intermittent connectivity issues to Okta caused by Azure SNAT port limits.