As per my knowledge, there are no ways to hide it.
Well, you can't hide it, but you should be able to programmatically update it to an service account id using the REST API. https://onlinehelp.tableau.com/current/api/rest_api/en-us/help.htm#REST/rest_api_ref.htm#Update_Datasource_Connection%3F…
thanks tushar, I hope there are some configuration for server admin to do this thing for all users
while a custom portal is an option, I'm not suggesting this in the above post. I was just suggesting a small utility that leverages the REST API to update all the db connections to a generic service account id that also has access. May I ask what is the security concern in the first place of displaying the username?
Hi Jeff Strauss
Actually I don't understand about what you mean above, small utility.. to a generic service account id. Could you please give me more brief with that?
In my company, there are some policy from our security dept. to protect all the information access such as DB IP/server name, DB username and password, etc. Just like any other web app, users only sign in with their credentials (username & pwd) without they have to know the Database IP/name, Database username and other connection string to the DB.
Unfortunately, in datasource information (pict that I post), it shows everything that restricted with our company rules. I hope there are some configuration whether show/not that information to the users.
1 of 1 people found this helpful
As far as I know there is no way to hide this info, but here are some indirect workarounds (both with limitations) if there's no way around your company's policy.
In order of ascending pain-factor.....
1. Point all your workbooks (where you want to hide the connection info) to published data sources - then move these data sources to another project and set the permissions such that the users can't access this project. This will result in the users still being able to view the workbooks, but not the published data source connection info
2. Use Tableau SDK/Extract API to create extract files from your DB outside Tableau and then publish them up......that way they will not contain any connection lineage info
Justin, these are great ideas!!!! Thanks for posting them here.
Just wondering, so if you have implemented this - "Use Tableau SDK/Extract API to create extract files from your DB outside Tableau and then publish them up......that way they will not contain any connection lineage info" as answered by Justin,
- HOW ARE YOU UPDATING THE EXTRACTS? DO YOU NEED TO DO IT?
My another question is it possible to link the extracts with a live source and send both data, TDE and Live Connection Link, to Server?
My issue is Add Live Data Source To Tableau Server From CODE
You would need to update the server datasources using the tabcmd "publish" command - my understanding is that you can also run this command via Tableau's REST API but I haven't tried that.
Sorry, I'm not sure I understand the second part of that question.....I think the Tableau SDK might be a dead end though if you need to create live connects to the backend data source.
I think you can create data source in tableau server that connect live to your database. From this point, you can blend your data from extract and live.
if you mean that you want to join with extract, I don't think is going to work
I would really appreciate if you can point me to somewhere/anywhere on HOW TO DO THIS " create data source in tableau server that connect live to your database".
There aren't any resources regarding this, I can't find any relevant ones.
Yes, updating the extracts can be done, I think through the REST API. What I am looking for is creating a live connection from CODE, NOT TABLEAU DESKTOP, and send that connection to TABLEAU SERVER.