Use the OAuth Authorizer to authorize with an OAuth2 service. OAuth2 is sometimes called Modern Authentication.
You can use the OAuth Authorizer to show bearer and refresh tokens after authorization. This is useful when setting up a trigger script that needs to make an OAuth protected API call.
|Preset||Select a preset to use. If your service is not there please select ‘Custom Settings’. Selecting a preset will gray out the fields that have known values for that preset.|
|Client ID / Client Secret||The client ID and client secret of your application.
To use OAuth2 you’ll have to register your application with the service that you want to use. You should always receive a client ID after registration and may receive a client secret.
More on how to setup a client secret for Google and Microsoft.
|Scope||The scope of the permissions that you need. This is specific to the server that you’re authorizing for.|
|Flow||This can be either:
The best option for your use case differs depending on the service.
|Redirect URL||This setting applies only to the ‘Authorization Code Flow’. This URL does not need to be accessible from outside of the organization. The OAuth Authorizer listens on this URL to receive the authorization tokens.
Listening on the redirect URL uses the HTTP.sys HTTP server that is built into MS Windows. This needs to be configured using the ‘Configure…’ button that shows the NetSh Express setup.
|Auth. Code URL||The Authorization Code URL only applies to the ‘Authorization Code Flow’. This URL should initially redirect to the login page for the service. This URL depends on the service.|
|Device Code URL||The device code URL only applies to the ‘Device Code Flow’. This URL should start the device code flow. This URL depends on the service.|
|Token Ex. URL||The token exchange URL is used to exchange the authorization code token for the bearer token. When this dialog is used for the e-mail channels this URL is used again to exchange the refresh token for a new bearer token. This URL depends on the service.|