Tableau Cloud Provisioning Error "Errors reported by remote server: Bad Request: Invalid filter value passed"
Last Updated:
Overview
This article brings more context and a possible solution to a provisioning error that might be encountered when trying to assign users to the Tableau Cloud application:
Automatic provisioning of user <User Name> to app Tableau Cloud failed: Error while verifying if user <<username>> exists: Errors reported by remote server: Bad Request: Invalid filter value passed
Applies To
- Provisioning
- Tableau Cloud Application
- Okta Integration Network (OIN)
- New users assigned to the Tableau Cloud Application
Cause
When trying to assign new users through Okta provisioning, Okta has a two-step plan for determining whether a new user needs to be created or if it should match an already existing user.
Okta will use an API call to first query whether the user with the username provided in the application assignment already exists. If no matching user is found, Okta will proceed to create a new one.
In this use case, provisioning fails on the API call to query if the user should exist, because the filters used on that back-end API call are being recognized as invalid by Tableau Cloud's SCIM server. Here is how an API call on the back-end usually looks:
https://scim.online.tableau.com/pods/prod-useast-a/sites/<<tableau-cloud-site>>/scim/v2/Users?filter=userName%20eq%20%22username%40domain.com%22&startIndex=1&count=100
Tableau Cloud may recognise the ?filter=userName... section as invalid due to the filters created to convert the username provided in a URL format.
Solution
To fix this, a change to the username provided is needed to apply different filters that Tableau Online recognizes as valid:
- Navigate to Admin Console > Applications > Applications > Tableau Cloud.
- On the Assignments tab, search for the affected user, and click on the pencil icon on the right.
- At the top, change the username of the user by:
- Removing capital letters.
- Make sure that no spaces can be found at the username's start or end.
- Make sure that no special characters such as <, >, ?, {, [, etc., are present.
If a custom expression is used to create the username, please make sure to edit the attributes used to build the username so that the change is propagated to the user.
