Obtain access token using the Configuration Manager
- Last Updated: May 13, 2025
- 2 minute read
- DataDirect Connectors
- JDBC
- GitHub 6.0
- Documentation
You need the following information before you begin.
- Server Name - the endpoint of the GitHub service to which you are connecting
- Auth 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
- Client ID - the client ID for your application
- Client Secret - the client secret for your application
- Scope - an OAuth scope, or a space-separated list of OAuth scopes, which specifies the permissions that limit application access to the GitHub service.
The following steps describe how you can use the Progress DataDirect GitHub Configuration Manager to obtain access token for the access token flow grant. In addition, the Configuration Manager produces a connection URL that you can use in your application.
Results:
The Access Token field includes access 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 JDBC application to connect with your GitHub service.
Note:
Not all the values in the resulting connection string are required. However, the connection string can be copied directly into your JDBC application. The driver ignores any values that do not apply to your OAuth implementation.
For example, the access token grant connection string, derived from the Configuration Manager, might include the following properties.
jdbc:datadirect:github:ServerName=server_name;
AuthURI=auth_uri;TokenURI=token_uri;
ClientID=client_id;ClientSecret=client_secret;
AccessToken=access_token;Scope=scope;
However, only the following properties are required for an access token grant connection string.
jdbc:datadirect:github:ServerName=server_name;
TokenURI=token_uri;ClientID=client_id;
ClientSecret=client_secret;AccessToken=access_token;