Supported Authentication

Here are the supported authentication types with Content Gateway:

API Key Auth

API Key authentication entails sending an API key in the header. To set this up, please provide the following auth info in your gateway:

Required Info

• API Key: This is where we'll input your actual API key value. This will be sent as the value for the Authorization Header key.

Additional Info

• Custom Base Url: In case you have a different custom base URL for the connector, you can specify it here.

OAuth 2.0 with Grant Type : 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 as a Bearer Token, to authenticate the API Request.

To set this up, please provide support the following auth info in your gateway:

Required Info

• Client ID: This is where we'll input your actual Client ID value.

• Client Secret: This is where we'll input your actual Client Secret value.

• Oauth2 Token Url: This is where we'll input the full token URL.

Additional Info

• Client Authentication Method: Moveworks will try making the request with both Basic Auth and Request Body Auth by default.
• Custom Base Url: In case you have a different custom base URL for the connector, you can specify it here.
• Encrypter Authentication Header: If needed, you can configure additional headers for the auth request.
  • Data will be sent in the header like so:
  JSON

  curl --location 'URL' \
  --header 'x-api-key: <YOUR-ENCRYPTED-KEY-HERE>'
  

On-Prem Auth

You can additionally create new on-prem agent connections to authenticate into your Content Gateway.