#Snowflake5 discussing

Environment: Tableau Cloud, REST API 3.29, tableauserverclient (Python), Snowflake connection with authentication='oauth', oauth-config-id='default', server-oauth='server-custom'. 

ISSUE 

We publish workbooks via REST API/PAT in a CI/CD pipeline. We're trying to reproduce a connection state that Tableau Desktop can produce, but the REST API can't. 

Desktop-published state (Data Sources tab shows "Not embedded in connection"): 

auth_type='oauth' username='<user>' embed_password=False 

Our pipeline's state (REST API publish): 

auth_type='oauth' username='' embed_password=False 

The Desktop state results in viewers being prompted for their own credentials. Ours results in every viewer getting BadOAuthCredentials, since there's no username hint at all. 

WHAT WE TRIED 

Using Server.workbooks.update_connection() (PUT /workbooks/{id}/connections/{connectionId}), we tested every combination: 

1. embed_password=True + username -> credential embeds, all viewers connect silently as that one identity (no prompt). 

2. embed_password=False + blank username -> every viewer gets BadOAuthCredentials. 

3. embed_password=False + non-empty username (trying to match Desktop) -> the server silently discards the username; a follow-up GET always returns username=''. No error is returned, it just reverts. 

4. Re-embedding (embed_password=True) via update_connection without supplying a password fails outright with 404020: Resource Not Found ... This may be due to incorrect or missing credentials. There's no way to flip an OAuth connection back to embedded through this endpoint without a real credential, and OAuth connections have no password-style credential the API can supply. 

We confirmed #3 fails identically whether attempted via connections=[ConnectionCredentials(...)] at publish time, or via a separate post-publish update_connection call. Same result both ways. 

QUESTIONS 

1. Is there any documented REST API mechanism (any endpoint, any API version) to set an OAuth connection to embedPassword=false while preserving a non-empty userName hint, matching what Desktop produces? 

2. Is that "not embedded + username hint" state inherently tied to an interactive/vizportal-authenticated session (i.e. genuinely unreachable via PAT/REST), or is there an undocumented parameter/flow we're missing? 

3. Is per-viewer OAuth prompting for a Snowflake connection with oauth-config-id='default' expected to work at all when the workbook was published via REST API/PAT, or is this a Desktop-only capability? 

Happy to share full request/response payloads if that helps with diagnosis. 

#OAuth  #Tableau APIs & Embedding

#Tableau Cloud  #Tableau Server

When I click to edit a data source, I get this pop-up:

I then click on Connect, and the pop-up disappears, but otherwise nothing else happens. 

So I try again and click on Edit Data Source Credentials, which brings me to this screen:

Then I click on the "Sign In" button and get this error message:

I am logged into Snowflake and Tableau Cloud this whole time. I have tried clearing saved server sign-ins via Help>Settings and Performance in Desktop, and then restarting, but I get the same error. I have tried removing and re-adding the Snowflake saved credentials on Tableau Cloud, but that doesn't fix anything. 

I can use the same Snowflake credentials to create a new data source in the same Tableau Desktop workbook, and even go back in and edit that new data source, but I can't edit any data sources from before without getting this pop-up. I can also edit those same data sources on Tableau Cloud without issue, but not in Desktop. 

Not sure what to do here. Any ideas?