- Newest
- Most votes
- Most comments
To establish an ODBC connection between Tableau and Amazon Redshift Serverless using Okta OIDC authentication, you'll need to configure specific parameters in the ODBC v2 driver. Here are the key parameters you should set:
-
Auth_Type: Set this to "identity_provider_oauth" to use Okta OIDC authentication.
-
IdP_Host: This should be your Okta domain (e.g., your-company.okta.com).
-
IdP_Tenant: Your Okta tenant ID.
-
Client_ID: The client ID of your Okta OIDC application.
-
Client_Secret: The client secret of your Okta OIDC application.
-
Scope: Set this to "openid profile email".
-
ClusterID: Your Redshift Serverless workgroup name.
-
Region: The AWS region where your Redshift Serverless cluster is located.
-
Database: The name of the database you want to connect to.
-
SSL_Insecure: Set to "true" if you're using a custom DNS name with PrivateLink.
To configure these parameters in Tableau Server's web interface:
-
Log in to Tableau Server as an administrator.
-
Go to the "Settings" or "Connections" section.
-
Look for an option to add or edit a data source connection.
-
Choose Amazon Redshift as the connection type.
-
In the connection details, you should see an option for "Advanced" or "Additional Parameters".
-
In this section, you can enter the ODBC connection string with the parameters listed above. The format would be similar to:
"Auth_Type=identity_provider_oauth;IdP_Host=your-company.okta.com;IdP_Tenant=your-tenant-id;Client_ID=your-client-id;Client_Secret=your-client-secret;Scope=openid profile email;ClusterID=your-workgroup-name;Region=your-region;Database=your-database;SSL_Insecure=true"
-
Save the connection settings.
Remember to replace the placeholder values with your actual Okta and Redshift Serverless configuration details. Also, ensure that your custom DNS name for the PrivateLink connection is properly configured and resolves to the Redshift Serverless endpoint.
If you encounter any issues, you may need to consult with your network administrator to ensure that the PrivateLink connection is properly set up and that Tableau Server has the necessary network access to reach both Okta and your Redshift Serverless cluster.
Sources
Federate IAM-based single sign-on to Amazon Redshift role-based access control with Okta | AWS Big Data Blog
Integrate Tableau and Okta with Amazon Redshift using AWS IAM Identity Center | AWS Big Data Blog
Okta - Amazon Redshift
Configuring an ODBC driver version 1.x connection - Amazon Redshift
answered 2 years ago
Dear Customer,
To configure the ODBC v2 connection parameters for Redshift Serverless using Okta OIDC authentication in Tableau Server, you'll need to provide several key parameters. Here's a guide on what parameters to use and how to configure them in Tableau Server:
Parameters for ODBC v2 driver:
- Driver={Amazon Redshift (x64)}
- Server=your_custom_dns_name/workgroup endpoint
- Database=your_database_name
- Port=5439 (or your custom port if different)
- IAM=1
- Plugin_Name=okta_idp
- IdP_Host=your_okta_domain.okta.com
- IdP_Port=443
- Client_ID=your_okta_client_id
- Client_Secret=your_okta_client_secret
- Preferred_Role=your_preferred_iam_role_arn
- SSL=true
- SSL_Insecure=false
Configuring in Tableau Server (web interface):
-
Log in to Tableau Server as an administrator.
-
Go to "Settings" > "Connections" > "Add Connection".
-
Select "Amazon Redshift" as the connection type.
-
In the connection dialog:
- For "Server", enter your custom DNS name.
- For "Port", enter 5439 (or your custom port).
- For "Database", enter your database name.
- For "Authentication", select "Sign in using OAuth".
-
In the "Sign In" dialog, you may need to enter your Okta credentials.
-
After successful authentication, you'll be prompted to select a role. Choose the appropriate IAM role.
-
For additional connection properties, click on "Advanced" and add the following in the "Additional Connections Options" field: IAM=1;Plugin_Name=okta_idp;IdP_Host=your_okta_domain.okta.com;IdP_Port=443;Client_ID=your_okta_client_id;Client_Secret=your_okta_client_secret;Preferred_Role=your_preferred_iam_role_arn;SSL=true;SSL_Insecure=false Replace the placeholders with your actual values.
-
Test the connection and save it if successful.
answered 2 years ago
Relevant content
asked 3 years ago
- AWS OFFICIALUpdated 9 days ago

I believe ClusterID is for provisioned cluster, and there sould be something that would tell driver that this is serverless and Workgroup name or arn needs to be provided