The refresh token grant is used to replace expired access tokens with active ones by exchanging the refresh token at the endpoint specified by the Token URI connection option.

Note: The strings demonstrated in this section use the DSN-less format. For additional formats, see "Using a connection string."
Note: On Windows platforms, as opposed to using a third-party application such as Postman, you can use the Progress DataDirect HubSpot Configuration Manager to obtain a refresh token to support the refresh token grant. See "Obtaining access and refresh tokens using the Configuration Manger" for details. Alternatively, you can obtain a refresh token from HubSpot. Refer to the HubSpot documentation at https://help.hubspot.com for details.
DRIVER=DataDirect 8.0 HubSpot;ClientID=client_id;ClientSecret=client_secret;
RefreshToken=refresh_token;[attribute=value[;...]];

where:

client_id

specifies the client ID key for your application when authenticating with OAuth 2.0.

client_secret

specifies the client secret for your application when authenticating with OAuth 2.0.

refresh_token

specifies the refresh token for your application when authenticating with OAuth 2.0.

attribute=value
specifies connection option settings. Multiple option attributes are separated by a semi-colon.

The following example connection string includes the options for connecting with the OAuth 2.0 refresh token grant.

DRIVER=DataDirect 8.0 HubSpot;ClientID=29453d6f-6789-25gh-gd8g-44tk3c527831;
ClientSecret=12a3=bCD/EfGh4Ijk+Lm5P67qR8s=//TuV+WXy1Zabcd;
RefreshToken=12a3=bCD/EfGh4Ijk+Lgd8g-44tk3c527831;