Custom Credentials
When to Use a Custom OAuth App
Creating a custom OAuth app is required in the web flow. Creating a custom OAuth app is optional for desktop and headless applications; the driver is already registered with Wave Financial and you can connect with its embedded credentials. Creating a custom OAuth app is optional as the driver is already registered with Wave Financial and you can connect with its embedded credentials.You might want to create a custom OAuth app to change the information displayed when users log into Wave Financial to grant permissions to the driver.
Desktop Authentication with a Custom OAuth App
After Creating a Custom OAuth App, follow the steps below to authenticate with the credentials for a custom OAuth app.Get and Refresh the OAuth Access Token
After setting the following, you are ready to connect:
- OAuthClientId: Set to the client Id assigned when you registered your app.
- OAuthClientSecret: Set to the client secret assigned when you registered your app.
- CallbackURL: Set to the redirect URI defined when you registered your app.
- InitiateOAuth: Set to GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
- Extracts the access token from the callback URL and authenticates requests.
- Refreshes the access token when it expires.
- Saves OAuth values in OAuthSettingsLocation to be persisted across connections.
Web Authentication with a Custom OAuth App
When connecting via a Web application, you need to register a custom OAuth app with Wave Financial. See Creating a Custom OAuth App. You can then use the driver to get and manage the OAuth token values.
Get an OAuth Access Token
Set the following connection properties to obtain the OAuthAccessToken:
- OAuthClientId: Set to the Client Id in your app settings.
- OAuthClientSecret: Set to the Client Secret in your app settings.
You can then call stored procedures to complete the OAuth exchange:
-
Call the GetOAuthAuthorizationURL stored procedure. Set the AuthMode input to WEB and set the CallbackURL input to the Redirect URI you specified in your app settings.
The stored procedure returns the URL to the OAuth endpoint.
- Open the URL, log in, and authorize the application. You are redirected back to the callback URL.
- Call the GetOAuthAccessToken stored procedure. Set the AuthMode input to WEB. Set the Verifier input to the "code" parameter in the query string of the callback URL.
Refresh the OAuth Access Token
You can set InitiateOAuth to REFRESH to automatically refresh the OAuth access token when it expires, or you can call the RefreshOAuthAccessToken stored procedure to refresh the token manually.
Automatic Refresh
To refresh the token with InitiateOAuth, set the following on the first data connection:
- OAuthAccessToken: Set to the access token returned by GetOAuthAccessToken.
- InitiateOAuth: Set to REFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
- OAuthSettingsLocation: Set to the path where the driver will save the OAuth values, to be persisted across connections.
- OAuthClientId: Set to the Client Id in your app settings.
- OAuthClientSecret: Set to the Client Secret in your app settings.
- OAuthRefreshToken: Set to the refresh token returned by GetOAuthAccessToken.
On subsequent data connections, set the following:
- InitiateOAuth
- OAuthSettingsLocation
Manual Refresh
You can use the RefreshOAuthAccessToken stored procedure to manually refresh the OAuthAccessToken. Call the stored procedure after the ExpiresIn parameter value returned by GetOAuthAccessToken has elapsed. You need the following connection properties to be set:
- OAuthClientId: Set to the Client Id in your app settings.
- OAuthClientSecret: Set to the Client Secret in your app settings.
You can then call RefreshOAuthAccessToken with the following parameter set:
- OAuthRefreshToken: Set this to the OAuthRefreshToken returned by GetOAuthAccessToken.