Loading

Security Change: PKCE, Refresh Token Rotation, and Proof-of-Possession - Enforcement and Restrictions for Select Apps

Publiseringsdato: Nov 14, 2026
Beskrivelse

For select non-compliant connected apps and external client apps, Salesforce turns on and locks PKCE and Refresh Token Rotation security controls. Salesforce doesn’t turn on Proof-of-Possession (PoP) controls for your apps, but will block the app from being installed in other orgs until you turn on and lock at least one Proof-of-Possession (PoP) control. 

You can check the Insights page in Setup for per-app security control status.

This article doesn’t include enforcement dates. Salesforce communicates these dates separately via email.

Apps that are not selected are not affected by the change. Instead, refer to the other related change that affects all other apps: Security Change: PKCE, Refresh Token Rotation, and Proof-of-Possession - Restricting Installation of All Non-Compliant Apps. 

Løsning

What's Changing

On your app's enforcement date, Salesforce turns on and locks these two controls in your app’s OAuth settings:

  • Enable Refresh Token Rotation
  • Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows

Salesforce does not turn on a proof-of-possession (PoP) control, but will place restrictions on installing the app in other orgs until you enable and lock one of these controls:

  • Enforce Refresh Token IP Allowlist or 
  • Require DPoP (Demonstrating Proof-of-Possession). 

An app is compliant when all of the following are true:

  • Enable Refresh Token Rotation is enabled and locked.
  • Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows is enabled and locked.
  • Either Enforce Refresh Token IP Allowlist or Require DPoP (Demonstrating Proof-of-Possession) is enabled and locked. Note: Salesforce plans to introduce additional proof-of-possession control options in future releases.

Why Salesforce Is Making This Change

These controls help prevent attacks that use a copied or stolen OAuth token or authorization code to get access to your Salesforce data.

When This Change Takes Effect

Salesforce will communicate via email to app owners and admins each app's date separately.

Beginning late February, you can also view the enforcement date for an eligible app on the Insights page in Setup.

Salesforce Support doesn’t have information about your enforcement dates.  Do not contact Support to ask for your enforcement date. 

What the OAuth Security Controls Do

Control

What it prevents

What you update

Who this applies to

Refresh Token Rotation (RTR)

Reuse of a stolen refresh token

Update client-side code to save the new refresh token returned on every refresh.

Apps that use the refresh token flow. Nothing changes for an app that never requests a refresh token.

PKCE

Someone else using an intercepted authorization code to get an access token

Update client-side code to generate code_challenge and code_verifier parameters. Send the code_challenge in the authorization code request and the code_verifier in the token request.

Apps that use the authorization code grant type, including the web-server flow, hybrid web-server flow, and headless identity flows. No effect on apps that don’t  use these flows.

 

 

 

One proof-of-possession (PoP) control

Refresh token IP allowlist

Use of a stolen refresh token from a network that you didn’t approve

Update your app settings to allowlist IP ranges. Recommended for web apps with stable outbound IP addresses.

Every app needs at least one proof-of-possession control.

DPoP

Use of a stolen token without the app's private key

Update client-side code to send proof-of-possession with each token request and API call. Recommended for apps without a stable IP address or a client certificate, including browser and mobile apps.

Every app needs at least one proof-of-possession control.

Which Apps Are Affected

Salesforce enforces this change on select existing connected apps and external client apps.

Please review the email communications which list any affected apps and their dates. The email subject being sent in November: “[For Selected Apps] November Connected App & External Client App Security Updates”

Apps that are not selected are not affected by the change. Instead, refer to the other related change that affects all other apps: Security Change: PKCE, Refresh Token Rotation, and Proof-of-Possession - Restricting Installation of All Non-Compliant Apps. 

What to Expect After the Enforcement Date

After the enforcement date for your app:

  • Salesforce turns on and locks Enable Refresh Token Rotation. Each time your app uses a refresh token, Salesforce invalidates the used token and issues a new one. Your client-side code must capture the new refresh token returned by the refresh token flow and store it securely. If it does not, your refresh token flows stop working.
  • Salesforce turns on and locks Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows. Your client-side code must generate and send code_challenge and code_verifier parameters. If it does not, your authorization code flows stop working.
  • Salesforce does not turn on PoP controls. If you have not enabled at least one: Enforce Refresh Token IP Allowlist or Require DPoP (Demonstrating Proof-of-Possession), the app cannot be installed in another org. The app keeps working where it is already used.
  • Two weeks before the app’s enforcement date, access tokens for an app that is still not compliant expire after 24 hours, so users sign in again each day.
  • When an end user authorizes a non-compliant app, they see a security notice on the authorization approval page.
  • If an app already implements PKCE or Refresh Token Rotation, that behavior does not change.

Before Enforcement: How to Prepare

Complete these steps before the enforcement date. Do them in a sandbox first, then in production.

  1. Review the Insights page in Setup. It shows your apps and their security control compliance status (red is non-compliant, green is compliant). For an app created outside your org, such as a packaged or third-party vendor app, contact the app developer because you can’t update their app settings and client-side code. Apps created outside your org list a Distribution State of Packaged or Installed. Apps created in your org list a Distribution State of Local.
  2. Update configurations, test, then enable the control for apps that you own. For each app, change the client-side code first and confirm the new behavior in a sandbox. Then turn on the matching setting for that app. For mobile apps that use the Salesforce Mobile SDK, upgrade your app to Mobile SDK 14.0 or above, migrate users who are already logged in to DPoP, and make sure most of your users are on the upgraded version before you turn on DPoP.
    1. PKCE: See Enabling PKCE for OAuth for Salesforce External Client and Connected Apps.
    2. Refresh Token Rotation: See Enforce One-Time-Use Refresh Tokens with Refresh Token Rotation (RTR) in Salesforce.
    3. Proof-of-possession (PoP) control: Choose one of the following.
      1. For web apps with stable outbound IP addresses, use a refresh token IP allowlist.. See Restrict Refresh Tokens by IP Address.
      2. For apps without a stable IP address, use OAuth 2.0 Demonstrating Proof-of-Possession (DPoP). See OAuth 2.0 DPoP Guide and OAuth 2.0 DPoP Supported Flows and Endpoints
  3. Lock the controls. After all changes are implemented, you must lock the controls. After you lock each control and click Confirm, you can’t disable the security controls. The UI says "Review and lock security controls for Partner Applications," but the locking requirement also applies to non-partner apps.

After Enforcement: How to Resolve Errors

Open the Insights page in Setup in Setup and view the app's OAuth settings. Note any controls (PKCE, Refresh Token Rotation, or proof-of-possession) that are red as that means they are non-compliant.

Troubleshoot errors:

  • Reproduce the failed request and capture the OAuth error. See OAuth 2.0 Authorization Errors.
  • If refresh fails with an invalid or expired refresh token, the client is still replaying an old token or racing a second refresh. Store the newest refresh token and retry once with that token. See OAuth 2.0 Refresh Token Flow for Renewed Sessions.
  • If the token request fails PKCE validation, confirm code_challenge_method=S256 on the authorization request and that the token request sends the original code_verifier.

Contact Salesforce Support only to troubleshoot an error. Support can't waive or opt you out of the requirement for your app.

Common Questions

Will Salesforce turn these on for me?

Salesforce turns on and locks Refresh Token Rotation and PKCE for apps affected by this change. Salesforce cannot update your client-side code, so turn the controls on yourself before the date and test how they affect your integrations. Salesforce does not turn on a proof-of-possession control. After the change enforcement date, if you have not enabled and locked at least one proof-of-possession control, Salesforce will restrict installing the non-compliant app on new orgs. 

Which proof-of-possession control should I pick?

Use a refresh token IP allowlist for web apps that use the refresh token flow and have stable egress IPs. Use DPoP for server-to-server apps, apps that do not send tokens from a stable IP, or apps that do not use the refresh token flow.

Do I have to enable both DPoP and the IP allowlist?

No. Only one proof-of-possession control is required.

Do I have to review and lock the security controls?

Yes. Test that all integrations work with the new security controls turned on before locking each control because they can’t be disabled.

Where do I see my app's enforcement date?

Salesforce emails the app owner and org admins with details of the change, including the dates for their apps. Beginning late February, you can also check the Insights page in Setup. This article is not updated with per-app dates.

Can I keep creating connected apps?

New integrations should be external client apps. Starting in Spring '26, you can’t create new connected apps. See this knowledge article on connected app creation and the comparison of connected apps and external client apps.

I use an app from AppExchange or a managed package. What should I do?

Ask the vendor to enable PKCE, Refresh Token Rotation, and one proof-of-possession control, and to ship the client changes. Use the Insights page to check their compliance. Partner requirements are also described in Secure Your Connected Apps and External Client Apps in the ISVforce Guide.


Change Log

DateChange
November 14, 2026Initial publication

 

Flere ressurser

PKCE

Refresh Token Rotation (RTR)

Refresh Token IP Allowlist

DPoP

OAuth and CA/ECA General Resources

Knowledge-artikkelnummer

005466587

 
Laster
Salesforce Help | Article