Skip to main content
主题#Usernames

#Usernames3 人正在讨论

提问...
Ramandra Yadav 提问于 #OAuth 2.0
8月18日 12:30
Allow OAuth Username-Password Flows

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

2 个回答
  1. Kundan Kumar Jha (Infosys)
    8月19日 16:55

    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

撰写回答...
0/9000
Karen Starke
2018年7月25日 17:42

As we are working our way through the setup of Azure and Office 365 we have discovered an issue with the format of the UPN attribute in Active Directory for some of our users.  We have identified a fix for this; however, modification of this attribute could potentially impact software and applications that use this attribute for authentication. We have discovered Remedyforce-Salesforce is one of the Applications that will have an impact.

 

Our User logon names from AD was in the following format example : userid.dot.missouri and will now be changing to example : firstname.lastname@company.mo.gov. The things that will be causing us a couple issues  1. that means our username in Salesforce will change, creating a second user in Salesforce. Which we will have to disable all of them. Is there a way to fix this in Salesforce so that we can change the username without creating a second user or sending the customer a email saying there email address was changed? We currently have over 2600 users that will need to be changed. Is there a way to do this the with out having to disabling the old profile and pulling in the new? I have not found a easy way of disabling a profile either. Any Suggestions on this will be appreciated.  

1 条评论
  1. Paul Donders
    2018年8月14日 18:44

    No need to disable.

    The username can stay as is, as long as you set the unique principal name correct for sso in Salesforce.

    An other option is to just update the username based on the user Id. You could query them based on email for example.

    Hope this helps? Let me know if you have other questions.

撰写评论...
0/9000