Checked from this answer that, in case of tableau redirected you too many times, we first have to login to the tableau manually so that the logged in session in stored and then refresh the HTML page in which the tableau is embedded to load the tableau in HTML.
This seems to be little absurd/inconvenient. Is there a way to achieve that without any such efforts?
Check on other sites which says to clear cache/change content settings etc. My concern is that, when my application (which contains this embedded tableau) is hosted in a server, it would required all the application users to do all these manual processes. Which is not recommended.
Kindly help on a suitable suggestion on this. Thanks
I hope this will help someone in the near future.
The only thing to check on encountering this error is to know, whether you use a domain server/you have created your tableau credentials with a domain server.
The generic https://tableau/views/.. URL will not work, since the UI in which you are trying to embed the code, will hold the credentials that belongs to your domain and not the common domain of tableau. So, the tableau will be retrying you credentials in its common domain.
What you have to do is to concatenate the tableau with your domain like: https://tableau.ent.domain.lld.com/views/..
This will use your credentials to the tableau used on your domain server.
Hope this will help.
Related
I am pretty new to Tableau. I have a couple of tableau reports embedded in my react web project, but I don't want users to have direct access to my Tableau Online server.
From my research, I found Trusted Authentication, but I don't fully understand it and not sure whether Trusted Authentication is what I need.
Does anyone have any similar experience? Will Trusted Authentication prevent users from directly accessing my Tableau Online Server while still allowing embedding?
I am currently using tableau 9 version for my development purpose, same version tableau server as well. Currently I am using ldap authentication for the users to be added. In Tableau Server, I have given project level settings to restrict other department people. I have given interactor permissions for one of the user. But that user is able to access the whole site information(other projects as well) like a site admin rights.
Second issue I found that as, if we share the url with some other business unit member, they are able to access the url without any trouble (they are not added as ldap user in tableau site).
Please let me know if you face similar issues using tableau server ldap authentication.
Thanks!
I'm new to Tableau and was wondering if someone could explain to me how report data is secured when the report is embedded in a website or web application (e.g. ASP.NET)? From my research, it looks like there are two ways to embed a Tableau report:
Using an iFrame
Through the Tableau JavaScript API
Neither of these methods seem very secure, however, without requiring the user to log in to the Tableau server, which would require a double-login (first login to the web application and then a second login to the Tableau server) and thus be undesirable.
Can someone post a link, or otherwise help me to understand how security works with Tableau reports? I am really impressed with Tableau, but don't understand this aspect yet.
Thank you in advance.
Environment:
IIS server
ASP.NET MVC web application utilizing Windows Authentication
You'll want to look into using what Tableau calls "Trusted Authentication." There are a few methods they give you to accomplish this, so it will depend mostly on your configuration.
The general idea is that you authenticate once with Tableau server and it returns a ticket that you can use (usually for the duration of the session). With that, you can essentially imitate any user, so if you have user-specific data it will work as though they logged in.
You will need administrator access to your Tableau server to configure this.
Here are the docs for Trusted Authentication:
http://onlinehelp.tableau.com/current/server/en-us/trusted_auth.htm
It seems that basic functionality such as user login, can not be done in simple manner: to have username and password field in form on client and based on that to create store.readPathAccess model access rights. Also, how to check if user is logged in to implement access rights on routes?
Based on examples and (poor) DerbyJS documentation, if I understood it correctly, you have to implement login in server module (lib/server/*) because:
store.readPathAccess must be used in server side
you want to store data in model session (which can be read only on server side)
But many questions arise:
if it has to be done on server side, how to get and store client form data on server side without having problem with second item below on the list (I have done it with manually submitting data to server-only route, but can not then save it in model with local key because I have to redirect to client route after that and local model data is lost)
how to read later that data if it must be stored in session?
even if the store access rights for model is managed, how to check if this specific user is logged in when in client routes?
I'm quite confused at the moment... liked Derby principles, but this authentication problems are playing with my nerves seriously.
I know I may not be quite clear, but there are many points to go in details and if anyone can help I'll gladly give more required info.
Thank you,
Eddie
I found this library today called derby-auth.
It uses passport for signing in and has a good example using a simple register and login form.
What it does is to set some routes on the server for logging the user, and a middleware to tell the client if it's logged or not.
It does have some bugs (a few callback calls missing that break some things), so i wrote my own based on that, but must clean a lot of things before uploading anywhere.
i'd be glad to send it to you if you want to, though.
The most current library is https://github.com/derbyparty/derby-login
It has been updated pretty regularly and works with derbyjs 0.6
All,
I need to create an app for work that signs into our website using SSL and returns our member information.
I have figured out how to log in but am not sure how to find the id tags that I want to bring into my app and store to be show in a table view.
I know how to do these three things.
Put in username and password,
authenticate against website,
create session cookie.
Not sure how to do these things.
Get information about member, ie, how long a member , sustaining member, ect from the website knowing the tags for these fields on the site.
Store the data (core data?) or flat file. Shouldn't be that much information.
Format and present data in table view.
Lots of information here about getting files or whole websites but not so much about picking information off websites for concise viewing.
Thanks.
If your company's site is designed to provide this information through a web service, then it should be as simple as constructing your request URLs appropriately. If it has not been designed to interact with anything but humans, then you're probably going to have to do a great deal of work parsing HTML which no one can really help you with unless said site is publicly accessible.
Web Services should work fine with our website.