#Password3 personnes en discutent

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:

I was able to get it up and running.

I was change the required files in the config folder in tabjolt and was able to execute the custom scripts , get the postgres respository created and log in results . One thing would be handy is to have Java installed before hand set Environment Variables which can help you save some time.

This should be of great help.

Introducing TabJolt: A point-and-run load and performance testing solution for Tableau Server | Tableau Software

Tableau Desktop is only able to call authentication that is within the WDC itself (as documented at https://tableau.github.io/webdataconnector/docs/wdc_authentication). Any authentication prior to the WDC cannot be called through Tableau Desktop.

The reason of the difference observed when using the WDC Simulator (calls authentication pop-up) and Tableau Desktop (does not call authentication pop-up, and fails to connect) is that the simulator runs through a browser and has all the capabilities of the browser, including different approaches to authentication. Tableau Desktop itself has limited browser capabilities. The simulator is intended to be a tool to help with debugging WDC code, as opposed to a full replication of the WDC function.

In order to be able to connect Tableau Desktop to a target using SSO via WDC, the best course of action would be to move the authentication into the WDC itself and ensure that no other authentication requests occur before Tableau Desktop connects to the WDC.

If the above is not an option, please see k504866430 comment in https://github.com/tableau/webdataconnector/issues/160 . Basically Tableau can be programmed to capture the username, password and then construct the 'Authorization' header in javascript ajax request. for example:

fetch(url, {

method: 'GET',

headers: {'Authorization' : btoa($('⌗username').value + ":" + $('⌗password').value)} });

Should work.

Hello @Ciara Brennan​ 

I solved this problem by dividing the file into two.

And recently I had other problems with tabcmd publish. So I have 2 questions about tabcmd append.

At first, I would like to know the general case where tabcmd append fails.(ex. data shapes or column names are different each other)

Secondly, I wonder if it is possible to fail to append a file that is a big size of data.

I also have some uncomfortable cases when I execute tabcmd publish through the batch file.

The first case is that the modified time of the data source had been changed too late sometimes although the tabcmd publish batch file is completed. Especially this happens when I append over 10GB of data. I guess it took about 2 to 5 minutes.

The second case is that I everyday append 18GB of data using a batch file(about publish(append) of tabcmd) with the window scheduler. Sometimes, however, it has a fail once about every three months.

Hi @Sucharita Das​ 

If I am not wrong then you are talking about using the Passphrase along with SSH file.

The you get an option in SFTP to do that.

Save you file in the src/main/resource folder and then in SFTP do the below config:

Provide the Host, Port, Username, In Identity file provide the location where you shaved the file along with the file name (src/main/resource/<filename>), in Passphrase give the key you have for passphrase.

Regards,

Abhishek Bathwal