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.
On your app's enforcement date, Salesforce turns on and locks these two controls in your app’s OAuth settings:
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:
An app is compliant when all of the following are true:
These controls help prevent attacks that use a copied or stolen OAuth token or authorization code to get access to your Salesforce data.
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.
|
Control |
What it prevents |
What you update |
Who this applies to | |
|
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. | ||
|
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 |
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. | |
|
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. | ||
Salesforce enforces this change on select existing connected apps and external client apps.
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.
After the enforcement date for your app:
Complete these steps before the enforcement date. Do them in a sandbox first, then in production.
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.
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:
Contact Salesforce Support only to troubleshoot an error. Support can't waive or opt you out of the requirement for your app.
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.
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.
No. Only one proof-of-possession control is required.
Yes. Test that all integrations work with the new security controls turned on before locking each control because they can’t be disabled.
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.
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.
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.
| Date | Change |
|---|---|
| November 14, 2026 | Initial publication |
PKCE
Refresh Token Rotation (RTR)
Refresh Token IP Allowlist
DPoP
OAuth and CA/ECA General Resources
005466587

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.