This section describes how to edit the DSN configuration and then authenticate and connect to Talkdesk APIs.

DSN Configuration

You can use the Microsoft ODBC Data Source Administrator to edit the DSN configuration. Note that the installation process creates a both a user DSN and a system DSN, as described in Installing the Connector.

Note: The connector stores connection information in the Windows registry. To ensure that the connector can write to the registry, either run Power BI as an administrator or use a User DSN for your connection instead of a System DSN.

User DSN

Complete the following steps to edit the DSN configuration:

1. Select Start > Search, and enter ODBC Data Sources in the Search box.
2. Choose the version of the ODBC Administrator that corresponds to the bitness of your Power BI Desktop installation (32-bit or 64-bit).
3. Select the system data source and click Configure.
4. Edit the information on the Connection tab and click OK.

System DSN

Configure the system DSN the same way as the user DSN, except you will need to switch to the System DSN tab before performing Step 3.

If you're using Power BI's On-Premises Data Gateway with Standard mode, you must use the system DSN.

You must also specify a valid location for OAuthSettingsLocation (a path where OAuth credentials are locally stored to avoid repeated OAuth prompts).

This is because the Standard mode runs on service mode and can only access permitted locations, such as C:\Windows\ServiceProfiles\PBIEgwService\AppData\Local\Microsoft\On-premises data gateway.

Connecting to Talkdesk

To connect to Talkdesk, set the following properties:

• AccountName: The name of your Talkdesk account.
• Region: The region where your Talkdesk instance is deployed. Supported values are US (default), EU, CA, AU, UK, and FedRamp.
• OAuthClientId: The Client Id assigned when you registered your custom OAuth application.
• OAuthClientSecret: The Client Secret assigned to your custom OAuth application. See Creating a Custom OAuth Application for instructions on registering the application.

When you open the connection, the connector automatically requests an access token from Talkdesk and caches it. The token is refreshed automatically when it expires.

Authenticating to Talkdesk

Talkdesk supports the OAuth 2.0 Client Credentials grant flow. No browser-based authorization or callback URL is required.

OAuth Client Credentials

Authenticating with client credentials requires the creation of a custom OAuth application, as described in Creating a Custom OAuth Application.

To enable authentication, set these properties:

• AccountName: The name of your Talkdesk account.
• Region: The region where your Talkdesk instance is deployed. Supported values are US (default), EU, CA, AU, UK, and FedRamp.
• OAuthClientId: The Client Id assigned when you registered your OAuth application.
• OAuthClientSecret: The Client Secret assigned when you registered your OAuth application.

Use InitiateOAuth to control how the connector manages tokens:

• GETANDREFRESH (default): The connector requests a new access token on first connection and refreshes it automatically when it expires.
• REFRESH: The connector uses the token cached in OAuthSettingsLocation and refreshes it when needed. Use this setting after a prior GETANDREFRESH connection has populated the settings file.
• OFF: The connector does not request or refresh tokens. Provide a valid token via OAuthAccessToken and manage refresh yourself.

The OAuthSettingsLocation property specifies where the connector stores the cached access token. The default is OAuthSettings.txt in the current working directory. When using multiple connections with the same driver, set a distinct path for each connection to prevent one connection from overwriting another's cached token.