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

You need the following information before you begin.

  • Sample endpoint: The endpoint of the service to which you are connecting
  • 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.
  • Client ID: The client ID for your application.
  • Client Secret: The client secret for your application.
  • 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.
Note: You can also use the Autonomous REST Composer (administrator view) to obtain refresh tokens as described in this section. For general information on launching the Autonomous REST Composer, see "Getting started with prebuilt Model files" or "Generating a Model file with the Autonomous REST Composer."

The following steps describe how you can use the Progress DataDirect Autonomous REST Connector Configuration Manager to obtain an 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.

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

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

  2. Set Authentication Method to 24 (OAuth2).
  3. Provide the following information in the fields provided.
    • REST Sample Path
    • Authorization URI
    • Token URI
    • Client ID
    • Client Secret
    • Scope (if required by your REST service)
  4. Retrieve the access token.
    1. Click Fetch OAuth Token.
    2. If the logon popup appears, enter your credentials. (This popup may not appear if you previously logged on.)
    3. 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.)
    4. The Access Token and Refresh Token fields populate 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 and Refresh Token fields include the access tokens 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 application to connect with your REST 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 refresh token grant connection string, derived from the Configuration Manager, might include the following options.

DRIVER=DataDirect 8.0 Autonomous REST Connector;RESTConfigFile=filepath;
       AuthenticationMethod=24;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 refresh token grant connection string.

DRIVER=DataDirect 8.0 Autonomous REST Connector;RESTConfigFile=filepath;
       AuthenticationMethod=24;TokenURI=token_uri;ClientID=client_id;
       ClientSecret=client_secret;AccessToken=access_token;