<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

Disabling PKCE on an Okta OpenID Connect Client

API Access Management
Okta Classic Engine
Okta Identity Engine

Overview

Okta OIDC PKCE requirements depend on an app's ability to securely store a client secret. Single-Page Applications (SPAs) require PKCE, while it remains optional for Web and Native Applications. To disable it for the latter, simply adjust the client authentication options and clear the verification checkbox.

Applies To

  • Okta Identity Engine (OIE)
  • Okta Classic Engine
  • OpenID Connect (OIDC)
  • Authorization code flow
  • Proof Key for Code Exchange (PKCE)

Solution

Which Client Types Require PKCE?

Because Single-Page Applications (SPAs) run on-device and cannot securely store client secrets, Okta classifies them as public clients. To provide security, PKCE binds the authorization request to the token exchange. Consequently, Okta permanently enforces PKCE for all SPAs, and it cannot be disabled.

 

PKCE Is Optional for Web Applications and Native Applications

Okta classifies Web applications as confidential clients since they run on servers and securely store secrets, making PKCE optional. However, Okta still recommends enabling PKCE to prevent injection and CSRF attacks. This can be toggled via the "Require PKCE as additional verification" checkbox under General Settings.

pkce setting

 

How Is PKCE Disabled on Native Applications?

Okta enables PKCE by default on native apps since their default authentication is "none." To disable it:

  1. Set client authentication to Client secret or Public key / Private key.
  2. Clear the Require PKCE as additional verification checkbox.

 

Related References

Loading
Disabling PKCE on an Okta OpenID Connect Client | Okta Support