Loading
Slack 관련 문의처가 Salesforce Help로 통합 및 변경됩니다.더 많이 읽기

Security Change: Retirement of the OAuth 2.0 Username-Password Flow by February 20, 2027

게시 일자: Oct 14, 2026
상세 설명

Salesforce is retiring the OAuth 2.0 username-password flow for connected apps. After enforcement, connected app integrations that use this flow can no longer obtain access tokens. This update was first announced in Spring '26. See also the latest Summer '26 Release Note.

솔루션

This article answers the question: what is changing with the OAuth 2.0 username-password flow for Salesforce connected apps on February 20, 2027, and how do you prepare your integrations? It explains the change, who is affected, what to expect, and the steps to take before and after enforcement.

What's Changing

On February 20, 2027, Salesforce stops supporting the OAuth 2.0 username-password flow for connected apps. After enforcement, connected app integrations that use this flow can no longer obtain access tokens.

Why Is Salesforce Making This Change

The username-password flow sends a user's credentials directly in an HTTP request. Retiring this flow increases security and better protects your Salesforce data.

When Does This Change Take Effect

Salesforce enforces this update on February 20, 2027.

Who's Affected

This change applies to Lightning Experience and Salesforce Classic in all editions.

You're affected if a connected app integration uses the OAuth 2.0 username-password flow. This includes custom integrations and apps installed from managed packages.

If the Retirement of OAuth 2.0 Username-Password Flow for Connected Apps release update doesn't appear in your org, the flow is already blocked in your OAuth and OpenID Connect settings, and this change doesn't affect you.

What to Expect

After Salesforce blocks or retires the flow, the following behavior occurs:

  • Integrations that use the username-password flow can't obtain access tokens and stop working.
  • Login History shows the status OAuth Username-Password Flow Disabled for blocked attempts.
  • Token requests fail with the response shown below.
{
  "error": "invalid_grant",
  "error_description": "authentication failure"
}

In plain text, the failed token request returns the error invalid_grant with the description "authentication failure". The message shown to end users depends on how the app handles the failed token request.

Before Enforcement: How to Prepare

  1. Identify affected integrations by using Login History or a SOQL query.
  2. For integrations that support end-user login and authorization, migrate to the OAuth 2.0 web-server flow with the Proof Key for Code Exchange (PKCE) extension.
  3. For server-to-server integrations, migrate to the OAuth 2.0 client credentials flow.
  4. For apps that you didn't develop, contact the app developer and confirm that an updated version will be available before February 20, 2027.
  5. In a test environment, block the username-password flow and test each integration. Update any integration that fails.
  6. After all integrations work while the flow is blocked, deploy the changes to production.

For detailed testing and activation instructions, log in to your org. From Setup, in the Quick Find box, enter Release Updates, and then select Release Updates. Open Retirement of OAuth 2.0 Username-Password Flow for Connected Apps and follow the testing and activation steps.

Identify Apps That Use the Username-Password Flow


Option 1: Review Login History

  1. From Setup, in the Quick Find box, enter Login History, and then select Login History.
  2. Make sure the Login Subtype column appears. If it doesn't, edit the view or create a view that includes it.
  3. Find entries where Login Subtype is OAuth Username-Password.

Option 2: Run a SOQL Query

Use the English LoginSubType value exactly as shown.

SELECT Application
FROM LoginHistory
WHERE LoginSubType = 'OAuth Username-Password'

In plain text, this query returns the Application value from each LoginHistory record where the LoginSubType is OAuth Username-Password, which lists the apps that still use the username-password flow.

After Enforcement: Resolve Errors

Note: After Salesforce enforces this change on February 20, 2027, there is no opt-out. Re-enabling the username-password flow isn't a supported resolution.

  1. Review Login History for attempts with the OAuth Username-Password Flow Disabled status.
  2. Identify the affected connected app or integration.
  3. Update an end-user integration to use the OAuth 2.0 web-server flow with PKCE, or update a server-to-server integration to use the OAuth 2.0 client credentials flow.
  4. If you don't own the app, contact its developer for an updated version.
  5. Test the updated integration and confirm that token requests and business processes succeed.

Common Questions


Which OAuth 2.0 flow should I use instead of the username-password flow?

For end-user login and authorization, use the OAuth 2.0 web-server flow with the Proof Key for Code Exchange (PKCE) extension. For server-to-server integrations, use the OAuth 2.0 client credentials flow.

What if I can't update the integration because I'm not the app developer?

Contact the app developer and confirm that they will provide an updated version before February 20, 2027. Test the updated version before deploying it to production.

Why can't I see the Username-Password Flow release update in my org?

If the release update isn't listed, the username-password flow is already blocked in your OAuth and OpenID Connect settings. The retirement doesn't require further action for that org, but you should verify that your integrations are working as expected.

Knowledge 기사 번호

005461279

 
로드 중
Salesforce Help | Article