On March 30, 2027, Salesforce restricts new installations of any connected app (CA) or external client app (ECA) that doesn’t enable and lock the required OAuth security controls: Proof Key for Code Exchange (PKCE), Refresh Token Rotation (RTR), and at least one proof-of-possession (PoP) control. Existing connections keep working.
You can check the Insights page in Setup for per-app security control status.
Salesforce will block installing non-compliant connected apps (CA) or external client apps (ECA) to other orgs, while existing connections keep working and API access continues. An app is compliant when its OAuth settings meet these requirements:
Salesforce doesn’t turn on or lock these controls on for you. Until you enable the controls, Salesforce blocks all attempts to install the app in another org.
These controls help prevent attackers from using a copied or stolen OAuth token or authorization code to access your Salesforce data.
March 30, 2027 for all non-compliant connected apps and external client apps. Salesforce doesn’t support extensions for this change.
| 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 do not use these flows. | |
| Choose One proof-of-possession (PoP) control | Refresh token IP allowlist (one proof-of-possession control) | Use of a stolen refresh token from a network that you did not 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 (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. | |
This change applies to all connected apps and external client apps that have any non-compliant OAuth security controls.
For select apps, Salesforces requires stricter enforcement of these controls. This change is covered in a separate article, "Security Change: PKCE, Refresh Token Rotation, and Proof-of-Possession - Enforcement and Restrictions for Select Apps," and are not affected by this change.
How to Identify Security Control Compliance
Open the Insights page in Setup. The page shows apps local to your org and apps developed elsewhere (packaged or installed). A green indicator means the control is compliant. A red indicator means the control is non-compliant. For a third-party app, contact the developer.
Complete these steps before the enforcement date. Do them in a sandbox first, then in production.
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.
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.
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.
Under this change, Salesforce does not turn on Refresh Token Rotation, PKCE, or a proof-of-possession control. You turn them on. As part of this change, Salesforce only blocks a new install of an app that is not compliant.
For select apps that require stricter enforcement, Salesforce will turn on PKCE and RTR as part of a separate change. Refer to this article for details of that change: Security Change: PKCE, Refresh Token Rotation, and Proof-of-Possession - Enforcement & Restrictions for Select Apps.
No. Salesforce doesn’t allow extensions for this change.
Yes. Test that all integrations work with the security controls turned on before locking each control because they can’t be disabled.
Use a refresh token IP allowlist for web apps that use the refresh token flow and have stable egress IP addresses. Use DPoP for server-to-server apps, apps that don't send tokens from a stable IP address, or apps that don’t use the refresh token flow.
No. Only one proof-of-possession control is required.
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 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
005466577

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.