Creating a JDBC Data Source

You can create a JDBC data source to connect from your Java application using the CData JDBC Driver for Talkdesk.

Follow these steps:

1. Add the driver JAR file to the classpath. The JAR file is located in the installation directory's lib subfolder. Ensure that the .lic file is located in the same folder as the JAR file.
2. Provide the driver class. For example:
   

   cdata.jdbc.talkdesk.TalkdeskDriver

3. Provide the JDBC URL. For example:
   

   jdbc:talkdesk:AccountName=myAccount;Region=US;OAuthClientId=myClientId;OAuthClientSecret=myClientSecret;

   Or, if there is a conflict in your application between drivers using the same URL format, use this form to ensure that you are using the CData driver:
   

   jdbc:cdata:talkdesk:AccountName=myAccount;Region=US;OAuthClientId=myClientId;OAuthClientSecret=myClientSecret;

   Ensure that the URL starts with either jdbc:talkdesk: or jdbc:cdata:talkdesk:. The URL can include any of the connection properties in name-value pairs separated with semicolons.

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 driver 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 driver manages tokens:

• GETANDREFRESH (default): The driver requests a new access token on first connection and refreshes it automatically when it expires.
• REFRESH: The driver 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 driver does not request or refresh tokens. Provide a valid token via OAuthAccessToken and manage refresh yourself.

The OAuthSettingsLocation property specifies where the driver 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.