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!
Related
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.
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'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
I have a website which will be used to show dashboards created in Tableau Desktop and published in Tableau Online.
I wanted to use Tableau Javascript API to access the dashboard to show it to users, but I don't want my web users to login to Tableau online.
My question is simply that "Can Tableau Javascript API be used to login to Tableau Online in the background and then fetch dashboards/views from it..?"
Based on my reading of the authentication documentation, there are three options:
Tableau Public requires no authentication for users to see visualizations. Tradeoffs: visualizations are static and public, and your storage space is limited. Ref: this forum discussion.
Tableau Online requires user login.
Tableau Server requires
user login, unless you configure it to say that requests from your
web server are always from trusted users. (See Trusted Authentication.) But even then, I think the license agreement requires that they be licensed users. You can license Tableau Server by # of cores instead of # of users though, in which case Tableau Server allows you to set up a Guest user that can access views anonymously.
So the short answer to your question appears to be no, not with Tableau Online. You have other options, but you either have to live with Public's limits or you'll need your own server, running Tableau Server. Even then you'd need to pay for each user to be licensed to access the product, unless you purchase a license based on # of cores, not # of users.
I have an MVC2 site that now allows access to it via windows authentication and uses ASP.net Role provider to provide authorization. I am trying to come up with a way for the site to allow the user access to the site if his username is a member of certain groups so I won't have to sign up user in sql, but just sign up a group with access. Anybody have any idea how to do this? Is there a quick and dirty way? So far in my internet perusals I haven't found a quick and dirty way to do this? Any help would be great.
Thanks
Looking up Role/Group information for a User
ASP.NET provides a useful “Role Management” capability, which allows developers to map users into logical “Roles” that can then be used to better control end-user capabilities and authorization access. For example, as a developer I could create a role called “managers” for my web application, and then limit access to portions of the site to only those users within the “managers” role (note: I will be posting additional recipes in the future that discuss how to fully use the Role Management authorization and capabilities features more).
When using Windows Authentication, ASP.NET allows developers to create and populate roles from multiple sources. For example, a developer could setup the built-in ASP.NET 2.0 SqlRoleProvider to map Windows users to custom application roles that are store within a database. This approach is very useful for scenarios where there might be application-specific role mappings that don’t make sense to push into a centralized Active Directory tree/store.
ASP.NET also makes it easy to access central Windows and Active Directory group mappings from within an application as well. For example, if there is a Windows group on the Active Directory network called “DOMAIN\managers”, an ASP.NET application could lookup whether the current Windows authenticated user visiting the ASP.NET site belongs to this group by writing code like this:
If User.IsInRole("DOMAIN\managers") Then
Label1.Text = User.Identity.Name & " is a manager"
Else
Label1.Text = User.Identity.Name & " is not a manager"
End If
Note that the role/group look-up is done via the “User.IsInRole(rolename)” method that is a peer of the User.Identity.Name property.
src
http://weblogs.asp.net/scottgu/archive/2006/07/12/Recipe_3A00_-Enabling-Windows-Authentication-within-an-Intranet-ASP.NET-Web-application.aspx