Connect from Tableau Desktop with Authentication
On this page
Prerequisites
Connecting Tableau to the MongoDB Connector for BI requires the following:
Tableau version 10.3 or later
A running mongod instance or Atlas deployment
A running
mongosqld
instance running with authentication enabled using--auth
, or the BI Connector for Atlas enabled.
Connecting Tableau to the MongoDB Connector for BI requires the following:
Tableau version 10.4 or later
A running mongod instance or Atlas deployment
A running
mongosqld
instance running with authentication enabled using--auth
, or the BI Connector for Atlas enabled.
Procedure
Download and install the MongoDB BI Connector ODBC Driver.
Download the MongoDB BI Connector ODBC Driver and run the Windows installer (.msi
).
Create a system DSN.
To securely connect Tableau to the BI Connector, a system DSN configured to use the MongoDB BI Connector ODBC Driver is required. To create a system DSN, follow the steps below:
Start the Microsoft ODBC Data Sources program.
Choose the program version (64-bit or 32-bit) which is appropriate for your system and ODBC driver version.
Select the
System DSN
tab.Click the
Add
button.click to enlargeSelect a MongoDB BI Connector ODBC Driver from the list of available drivers.
Select either the MongoDB ODBC ANSI Driver or the MongoDB ODBC Unicode Driver, then click OK.
Note
The ANSI ODBC driver offers maximum performance but has a limited character set. The Unicode ODBC driver supports a wider character set but may be slightly less performant as a result.
Fill in the necessary form fields.
Click the Details button to expose the lower half of the form.
The following form fields are required:
Field NameDescriptionData Source NameA name of your choice.TCP/IP ServerAddress of the server where yourmongosqld
process is running. If you have enabled BI Connector on MongoDB Atlas, you can find the hostname of the server wheremongosqld
is running in the connection information for your cluster.PortPort number of yourmongosqld
process.DatabaseThe name of the database to connect to, e.g.test
.Provide connection information.
The following fields are required when running with
--auth
enabled or when connecting to an BI Connector for Atlas instance.Field NameDescriptionUserUsername of the MongoDB user who is authenticated to use your target database.
You can specify the following authentication options after your username as URI-style query parameters:
Connection OptionDescriptionsource
Specify the name of the database which stores the user's credentials. If you do not specify this option, the MongoDB Connector for BI will default to the current database associated with the MySQL connection.
For authentication mechanisms such as
PLAIN
(LDAP) orGSSAPI
(Kerberos) that delegate credential storage to other services, set thesource
value to$external
.Not required if
defaultSource
is set in your MongoDB Connector for BI configuration file.mechanism
Specify the mechanism that the MongoDB Connector for BI should use to authenticate the connection. Accepted values include:
SCRAM-SHA-1 (default)
PLAIN (LDAP SASL)
GSSAPI (Kerberos)
LDAP and Kerberos require MongoDB Enterprise. Set the source to
$external
when using LDAP or Kerberos.Not required if
defaultMechanism
is set in your MongoDB Connector for BI configuration file.X.509 is not supported.
For example, to authenticate as user
grace
using theadmin
database and the Challenge and Response (SCRAM-SHA-1
) authentication mechanism, write the username in this format:grace?source=admin For example, to authenticate as user
grace
with the LDAP (PLAIN
) authentication mechanism, write the username in this format:grace?mechanism=PLAIN&source=$external For example, to authenticate as user
grace
on theEXAMPLE.COM
Kerberos realm with the Kerberos authentication mechanism, write the username in this format:grace@EXAMPLE.COM?mechanism=GSSAPI&source=$external For more information about Kerberos configuration, see Configure Kerberos for BI Connector.
PasswordThe authenticated user's password.
You can't use curly braces (
{ }
) in your database password because these are special characters in the ODBC driver.AuthenticationThe default authentication method. When using the MongoDB BI Connector ODBC Driver, this field is not required.
To use the authentication plugin in conjunction with another ODBC driver, fill in this field with the string
mongosql_auth
.Click the
Test
button to test the ODBC connection.If the connection is successful, click OK to add the DSN. If the connection fails, check to make sure your MongoDB user is correctly authenticated for the database named in the connection.
Download and install the MongoDB BI Connector ODBC Driver.
Download the MongoDB BI Connector ODBC Driver and run the macOS installer (.dmg
).
Create a system DSN.
To securely connect Tableau to the BI Connector, a system DSN configured to use the MongoDB BI Connector ODBC Driver is required. To create a system DSN, follow the steps below:
Launch ODBC Manager.
Note
ODBC Manager is included with the MongoDB BI Connector ODBC Driver.
Important
The 1.0.16 edition of ODBC Manager included with the MongoDB BI Connector ODBC Driver is not compatible with macOS Catalina or later versions of macOS. If you are on Catalina or a later version of macOS, download and install the latest version (1.0.19) of ODBC manager.
Click System DSN, then click Add.
Select a MongoDB BI Connector ODBC Driver from the list of available drivers.
Select either the MongoDB ANSI ODBC driver or the MongoDB Unicode ODBC driver, then click OK.
Note
The ANSI ODBC driver offers maximum performance but has a limited character set. The Unicode ODBC driver supports a wider character set but may be slightly less performant as a result.
Enter a Data Source Name (DSN).
Optionally enter a Description.
Note
Do not close the setup window. Proceed to the next step.
Add the necessary keywords.
Add a keyword value pair by clicking the Add button.
Modify the Keyword by double-clicking on it, entering the desired keyword, then pressing enter.
Modify the Value by double-clicking on it, entering the desired keyword, then pressing enter.
Using the procedure above, add the following keywords:
KeywordValueSERVERThe hostname or IP address of the MongoDB Connector for BI host.
IMPORTANT: Use
127.0.0.1
to connect using TCP to localhost. If you specify a value other than an IP address, the BI Connector attempts to connect using Unix socket.PORTDATABASEThe database to use after connecting.
You must use this keyword when connecting with Microsoft Excel.
For the complete list of ODBC parameters, see Connector/ODBC Connection Parameters.
For example, your user DSN configuration should look similar to the following:
Note
Do not close the setup window. Proceed to the next step.
Add the authentication keywords.
Add a keyword value pair by clicking the Add button.
Modify the Keyword by double-clicking on it, entering the desired keyword, then pressing enter.
Modify the Value by double-clicking on it, entering the desired keyword, then pressing enter.
Using the procedure above, add the following keywords:
KeywordValueUIDThe username for the user that can access the active MongoDB Connector for BI database.
You can specify the following authentication options after your username as URI-style query parameters:
Connection OptionDescriptionsource
Specify the name of the database which stores the user's credentials. If you do not specify this option, the MongoDB Connector for BI will default to the current database associated with the MySQL connection.
For authentication mechanisms such as
PLAIN
(LDAP) orGSSAPI
(Kerberos) that delegate credential storage to other services, set thesource
value to$external
.Not required if
defaultSource
is set in your MongoDB Connector for BI configuration file.mechanism
Specify the mechanism that the MongoDB Connector for BI should use to authenticate the connection. Accepted values include:
SCRAM-SHA-1 (default)
PLAIN (LDAP SASL)
GSSAPI (Kerberos)
LDAP and Kerberos require MongoDB Enterprise. Set the source to
$external
when using LDAP or Kerberos.Not required if
defaultMechanism
is set in your MongoDB Connector for BI configuration file.X.509 is not supported.
For example, to authenticate as user
grace
using theadmin
database and the Challenge and Response (SCRAM-SHA-1
) authentication mechanism, write the username in this format:grace?source=admin For example, to authenticate as user
grace
with the LDAP (PLAIN
) authentication mechanism, write the username in this format:grace?mechanism=PLAIN&source=$external For example, to authenticate as user
grace
on theEXAMPLE.COM
Kerberos realm with the Kerberos authentication mechanism, write the username in this format:grace@EXAMPLE.COM?mechanism=GSSAPI&source=$external For more information about Kerberos configuration, see Configure Kerberos for BI Connector.
PWDThe password associated with the UID.
You can't use curly braces (
{ }
) in your database password because these are special characters in the ODBC driver.For the complete list of ODBC parameters, see Connector/ODBC Connection Parameters.
For example, your user DSN configuration should look similar to the following:
Click OK to finish creating the DSN.