Note: The Configuration Manager is currently supported only on Windows platforms.

You need the following information before you begin.

  • Host Name: The host name portion of the HTTP endpoint to which you are connecting.
  • Client ID: The client ID for your application.
  • Client Secret: The client secret for your application.
  • 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 to which the client is returned after third-party authorization for OAuth 2.0 implementations.
  • 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 an access token. In addition, the Configuration Manager produces a connection URL that you can use in your application.

Note: You must allow popups in your browser to obtain access token with the Configuration Manager.
  1. Open the GitHub Configuration Manager by selecting ODBC Administrator from the Progress DataDirect program group:

    For detailed information on launching the Configuration Manger, see "Configuring data sources with the Configuration Manger."

  2. Set Authentication Method to 24 (OAuth2).
  3. Provide the following information in the fields provided.
    • Host Name
    • Client ID
    • Client Secret
    • Authorization URI
    • Token URI
    • Redirect URI
    • Scope
  4. Retrieve the access token.
    1. Click Fetch OAuth Token.
    2. If consent popup appears, provide consent, allowing the Configuration Manager to retrieve the token. (This popup may not appear if you previously provided consent to the Configuration Manager.)
    3. The Access Token field populates with the value retrieved from the OAuth authorization server.
  5. Click Test Connect to verify connectivity and run SQL queries against the service.

Results:

The Access Token field includes the access token that you can use to implement OAuth 2.0.

The connection string in the Connection String field may be copied and used in your 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 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 access token flow connection string, derived from the Configuration Manager, might include the following options.

DRIVER=DataDirect 8.0 GitHub;HostName=host_name;
AuthURI=auth_uri;TokenURI=token_uri;RedirectURI=redirect_uri;
ClientID=client_id;ClientSecret=client_secret;
AccessToken=access_token;Scope=scope;

However, only the following options are required for an access token flow connection string.

DRIVER=DataDirect 8.0 GitHub;HostName=host_name;
AccessToken=access_token;