Publish to Tableau Tool v2.0 issues when CORS is enabled

[AStasi]

Version 2.0 of the publish to Tableau tool does not work for the initial authentication if Tableau Server has CORS enabled.  

This only impacts the UI for the tool that completes the sign in to Tableau Server and provides back the list of projects, data source names, etc. 

When CORS is enabled, a 403 error is received with a response of invalid CORS request.

If the XML on the tool is manually edited and the tool is run, it works fine to publish to Tableau, with or without CORS enabled. 

version 1.0.9 also works with no issues, but is not the ideal solution when users are on newer versions of Alteryx designer

Additionally calls to the REST API from a local desktop using postman or python work with or without CORS enabled. 

Based on conversations with Alteryx support, the tool was not tested with CORS enabled, thus the bundle.js file completing the authentication for the GUI must not account for Tableau Servers with CORS enabled. 

For those who build solutions with Tableau Server that utilize the REST API (e.g. like custom portals) CORS must be enabled to function, but it limits the ability to use version 2.0 of the publish to Tableau tool. 

[lmichela]

We need this!!!

[AStasi]

Follow up on this.  It appears that I can recreate the issue in postman when doing a call from my local machine.  It seems its all has to do with the code sending an origin header.  If the origin header isn't sent it works fine whether CORS is enabled or disabled on Tableau Server.   

[KylieF]

Thank you for submitting your idea to the Alteryx idea boards!

If you haven’t yet be sure to check out our updated Submission Guidelines as well as the other product idea boards! All boards are actively monitors and we appreciate all the feedback we receive for each product.

[ArunKumarL]

Need this as we want to enable CORS in tableau for other projects and this is stopping us.

[deepakantony329]

We also faced this issue and it was happening with all tableau tool versions.
We resolved the issue by adding "file://" to allow origin as origin was showing up as "file://".
TSM command:

tsm configuration set -k vizportal.rest_api.cors.allow_origin -v "https://mysite","https://yoursite","file://" 

This resolved the problem.