Obtaining access and refresh tokens using the Configuration Manager
- Last Updated: May 16, 2025
- 3 minute read
- DataDirect Connectors
- ODBC
- Snowflake 8.0
- Documentation
You need the following information before you begin.
- Authorization URI: The endpoint for obtaining an authorization code from a third-party authorization service
- Token URI: The endpoint used to exchange authentication credentials for access tokens
- Redirect URI: The endpoint that the client is returned to after authenticating with the service
- Client ID: The client ID for your application
- Client Secret: The client secret for your application
The following steps describe how you can use the Progress DataDirect Snowflake Configuration Manager to obtain access and refresh tokens for either the access token flow or the refresh token grant. In addition, the Configuration Manager produces a connection string that you can use in your application.
Results:
The Access Token and Refresh Token fields include access and refresh tokens that you can use to implement OAuth 2.0.
The connection string in the Connection String field may be copied and used in your ODBC application to connect with your service.
Note:
Not all the values in the resulting connection string are required. However, the connection string can be copied directly to a location that can be used by your application. The driver ignores any values that do not apply to your OAuth implementation.
For example, the connection string derived from the Configuration Manager might include the following options.
DRIVER=DataDirect 8.0 Snowflake;AccountName=account_name.us-east-1;
DatabaseName=MyDB;Schema=MySchema;Warehouse=accounting;AuthenticationMethod=24;
AuthURI=auth_uri;TokenURI=token_uri;ClientID=client_id;
ClientSecret=client_secret;AccessToken=access_token;
RefreshToken=refresh_token;
However, only the following options are required for a refresh token grant connection string.
DRIVER=DataDirect 8.0 Snowflake;AccountName=account_name.us-east-1;DatabaseName=MyDB;
Schema=MySchema;Warehouse=accounting;AuthenticationMethod=24;TokenURI=token_uri;
RedirectURI=redirect_uri;ClientID=client_id;
ClientSecret=client_secret;RefreshToken=refresh_token;