OAuth 2.0 - Client Credentials

OAuth 2.0 with Client Credentials grant type entails sending a valid Client ID and Client Secret in exchange for an Access Token. This Access Token is then used in subsequent requests, usually as a Bearer Token, to authenticate the API Request.

• To set this up, choose Oauth2 from the Auth Config dropdown list.
• Required Info :

• Oauth2 Grant Type: This should be set to Client Credentials Grant

• Client ID: This is where you input your actual Client ID value itself.

• Client Secret: This is where you input your actual Client Secret value itself.

• Client Credentials Grant Scope: This is where you can optionally input scopes associated with the OAuth credentials.

  • Note: Multiple scopes are separated by a single space

• Oauth2 Token Url: This is where you input the full token URL.

• Oauth2 Client Authentication: This can be left blank.
  Moveworks will try making the request with both Basic Auth and Request Body Auth by default.
• Header Auth Key, Header Auth Value Pattern, Oauth2 Custom Grant Type, Oauth2 Custom Oauth Request Options Custom Grant Type, Oauth2 Custom Oauth Request Options Additional Headers should all be left blank.
• If needed, you can leverage Oauth2 Custom Oauth Request Options Additional Request Data to send additional body data needed for the request.
  • Data is sent in x-www-form-urlencoded format in the body like so:

  1
  curl --location 'URL' \
  2
  --header 'Content-Type: application/x-www-form-urlencoded' \
  3
  --data-urlencode 'client_id=abcd-1234' \
  4
  --data-urlencode 'client_secret=secret123456' \
  5
  --data-urlencode 'Custom-body=abcde12345' \