-
1. Re: getFiltersAsync() returning a 403 using trusted authentication
Garrett Heaver Jun 28, 2016 6:15 AM (in response to Garrett Heaver)Digging in to this further. It appears to be a problem not only with trusted authentication. Indeed the same problem occurs when signed in to Tableau as an Interactor also
-
2. Re: getFiltersAsync() returning a 403 using trusted authentication
Garrett Heaver Jun 29, 2016 4:07 AM (in response to Garrett Heaver)Seeing this problem across the board the further I look at it. I have the same issue on Tableau 9.1 including calls to getFilterAsync(<filterName>). This includes listening to events such as...
viz.addEventListener(tableau.TableauEventName.FILTER_CHANGE, function(ev) {
ev.getFilterAsync().then(function(f) {
console.log(f);
});
});
They all generate a 403 from the server. Something very strange with that area of the JavaScript API or am I missing some major piece of information / configuration?
-
3. Re: getFiltersAsync() returning a 403 using trusted authentication
Andie Whitley LaMantiaSep 20, 2016 2:17 PM (in response to Garrett Heaver)
I'm not particularly well versed with JavaScript or the API, but it seems that this could be as simple as a problem with the Permissions for the logged in users.
When The API is run using a Tableau Server Administrator as the logged in user, Do you have the same problems? If you don't see the same problems, I'd probably fiddle around with the permissions for things like "Filter" (Permissions Reference).
-
4. Re: getFiltersAsync() returning a 403 using trusted authentication
Sankar Nair Jan 27, 2017 10:10 AM (in response to Garrett Heaver) -
5. Re: getFiltersAsync() returning a 403 using trusted authentication
Bill Lyons May 11, 2017 12:18 PM (in response to Sankar Nair)I would also note that I got this error when using getFiltersAsync() with Tableau Public when not logged in. After l logged in, this problem went away.