Connections

Back Next

OAuth 2.0 client credentials authentication

The following table describes the REST V2 connection properties for an OAuth 2.0 - Client Credentials authentication type connection:

Connection property	Description
Connection Name	Name of the connection. Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -, Maximum length is 255 characters.
Description	Description of the connection. Maximum length is 4000 characters.
Type	The REST V2 connection type.
Runtime Environment	Name of the runtime environment where you want to run the tasks. Select a Secure Agent, Hosted Agent, or serverless runtime environment. You cannot run a streaming ingestion task on a Hosted Agent or serverless runtime environment.
Authentication	The authentication method that the REST V2 Connector must use to connect to the REST endpoint. Select OAuth 2.0-Client Credentials .
Access Token URL	Access token URL configured in your application.
Client ID	Client ID of your application.
Client Secret	Client secret of your application.
Scope	Specifies access control if the API endpoint has defined custom scopes. Enter space separated scope attributes. For example: root_readonly root_readwrite manage_app_users
Access Token Parameters	Additional parameters to use with the access token URL. Parameters must be defined in the JSON format. For example, [{"Name":"resource","Value":"https://<serverName>"}]
Client Authentication	Select an option to send Client ID and Client Secret for authorization either in the request body or in the request header. Default is Send Client Credentials in Body .
Generate Access Token	Generates access token based on the information provided in the above fields.
Access Token	Enter the access token value or click Generate Access Token to populate the access token value. To pass the generate access token call through a proxy server, you must configure an unauthenticated proxy server at the Secure Agent level. The REST V2 connection-level proxy configuration does not apply to the generate access token call.
Swagger File Path	The path of the Swagger file or OpenAPI file. You can specify one of the following file paths: Absolute path along with the file name Hosted URL If you provide the absolute path of the swagger file or OpenAPI file, the file must be located on the Secure Agent machine. The hosted URL must return the content of the file without prompting for further authentication and redirection. For example, the path of the swagger file can be: C:\swagger\sampleSwagger.json The user must have the read permission for the folder and the file. In a streaming ingestion task, use only a hosted URL of the swagger specification file as the swagger file path.
TrustStore File Path	The absolute path of the truststore file that contains the TLS certificate to establish a one-way or two-way secure connection with the REST API. Specify a directory path that is available on each Secure Agent machinet. You can also configure the truststore file name and password as a JVM option or import the certificate to the following directory: <Secure Agent installation directory\jre\lib\security\cacerts . For the serverless runtime environment, specify the truststore file path in the serverless agent directory. For example, /home/cldagnt/SystemAgent/serverless/configurations/ssl_store/<cert_name>.jks
TrustStore Password	The password for the truststore file that contains the SSL certificate. You can also configure the truststore password as a JVM option.
KeyStore File Path	The absolute path of the keystore file that contains the keys and certificates required to establish a two-way secure communication with the REST API. Specify a directory path that is available on each Secure Agent machine. You can also configure the keystore file name and location as a JVM option or import the certificate to any directory. For the serverless runtime environment, specify the keystore file path in the serverless agent directory. For example, /home/cldagnt/SystemAgent/serverless/configurations/ssl_store/<cert_name>.jks
KeyStore Password	The password for the keystore file required for secure communication. You can also configure the keystore password as a JVM option.
Proxy Type	Type of proxy. You can select one of the following options: No Proxy: Bypasses the proxy server configured in the agent or the connection properties. Platform Proxy: Considers the proxy configured in the agent. Custom Proxy: Considers the proxy configured in the connection properties.
Proxy Configuration	The format required to configure proxy. You can configure proxy using the following format: <host>:<port> You cannot configure an authenticated proxy server.
Advanced Fields	Enter the arguments that the agent uses when connecting to a REST endpoint. You can specify the following arguments, each separated by a semicolon ( ; ): ConnectionTimeout . The wait time in milliseconds to get a response from a REST endpoint. The connection ends after the connection timeout is over. Default is the timeout defined in the endpoint API. If you define both the REST V2 connection timeout and the endpoint API timeout, the connection ends at the shortest defined timeout. connectiondelaytime . The delay time in milliseconds to send a request to a REST endpoint. Default is 10000. retryattempts . Number of times the connection is attempted when 400 and 500 series error codes are returned in the response. Default is 3. Specify 0 to disable the retry attempts. qualifiedSchema . Determines if the schema selected is qualified or unqualified. Default is false. For example, connectiondelaytime:10000;retryattempts:5 In a streaming ingestion task, only ConnectionTimeout and retryattempts are applicable.

Rename Saved Search

Table of Contents

Connections

Connections

OAuth 2.0 client credentials authentication

OAuth 2.0 client credentials authentication