We are performing a migration from a legacy Salesforce Username-Password OAuth integration to an External Client App using Client Credentials. To validate migration behavior, we need the org-wide setting "Allow OAuth Username-Password Flows"
enabled in our org. Could Salesforce Support confirm whether this setting can be enabled, whether any feature flags are required, and whether there are edition-specific restrictions preventing its availability?
#OAuth 2.0 #Usernames #Password #Flows #External Application
Hey Ramandra,
Himanshu's answer is accurate and matches what's actually being reported. Real-world evidence backs this up: even after explicitly turning on "Allow OAuth Username-Password Flows," users are still getting a "Username-Password Flow Disabled" error, confirming the toggle alone doesn't guarantee the flow will work, Salesforce's platform-level retirement enforcement can override it regardless of your org setting.
So to your three original questions:
- The setting existing and being toggleable doesn't mean the flow will actually function, this is confirmed behavior people are hitting even now
- Whether Support can override this for validation purposes is genuinely a case-by-case Support/AE conversation, not something the community can confirm
- Not edition-specific, it's the platform-wide retirement, not a licensing tier restriction
Practical suggestion: since you're already building the Client Credentials integration, validate it independently rather than trying to get the legacy flow re-enabled for a side-by-side. Compare against logs/behavior from your old integration instead of live-running both simultaneously, that avoids being blocked by something Salesforce is actively phasing out.
Reference:
https://help.salesforce.com/s/articleView?id=xcloud.remoteaccess_oauth_username_password_flow.htm&language=en_US&type=5
