Provide the login endpoint to initiate communication with the SaaS provider. For example, for the Adobe Experience Platform REST Application, the endpoint URL is https://platform.adobe.io.

You can bring your data into Adobe Experience Platform through streaming ingestion. Streaming ingestion allows you to send data from client and server-side devices to the Adobe Experience Platform in real time.

After registering a streaming connection you will have a unique URL which can be used to stream data to the Platform. The base path for streaming ingestion API for Data collection is: https://dcs.adobedc.net/.

The issuer, Organization ID from the Adobe I/O Console integration, in the format org_ident@AdobeOrg. Identifies your organization that has been configured for access to the Adobe I/O API.

The subject, your Technical Account ID from the Adobe I/O Console integration, in the format: id@techacct.adobe.com.

The keystore used to encrypt the JWT payload.

Use the same keystore which contains the private key of the certificate (Public keys) uploaded in your Integration in Adobe Experience Platform.

This alias is the value that is used to sign the outgoing request from Integration Cloud to the authentication server. It is auto-populated based on the keystore selected in the JWT Keystore field. This field lists all the aliases available in the chosen keystore. You must provide a key alias to sign the JWT payload.

Expiration Time (mins) is the time after which the JWT token expires. The generated access token might be valid post expiration time as well.

This token is used for authentication and is issued by the Authorization Server. The access token is passed when you invoke any of the REST API endpoints. The client application is responsible for storing and protecting this token.

Integration Cloud will get an Access Token using the JSON Web Token (JWT) Flow after you save the Account.

The audience for the token, your API Key from the Adobe I/O Console integration, in the format: https://ims-na1.adobelogin.com/c/api_key.

Consumer Key received from the app. Also referred to as the Client ID, this is a client identifier issued to the client to identify itself to the authorization server.

Consumer Secret received from the app. Also referred to as the Client Secret, this is a secret matching to the client identifier.

Adobe Experience Platform provides virtual sandbox environments which provide isolation and access control for Platform integrations. When making calls to Experience Platform APIs, a sandbox name must be supplied under the header x-sandbox-name. Provide the name of an available sandbox for your organization, for example, prod. The sandbox name is an all-lowercase identifier.

A token used by the client to obtain a new access token without involving the resource owner.

This is the provider specific URL to refresh an Access Token, for example, https://login.salesforce.com/services/oauth2/token.

The number of milliseconds Integration Cloud waits for a response before canceling its attempt to connect to the back end. In case the network is slow or the back end processing takes longer than usual, increase the Response Timeout value. It is recommended to specify a value other than 0. If you specify 0, Integration Cloud will wait indefinitely for a response.

The number of times Integration Cloud attempts to connect to the back end to read a response if the initial attempt fails. If an I/O error occurs, it will retry only if you have selected the Retry on Response Failure option.

Whether Integration Cloud should attempt to resend the request when the response has failed, even though the request was sent successfully. Select this option if you want to re-establish the connection.

The number of minutes you want Integration Cloud to wait before terminating an idle session. The session timeout value must be within the range of 10 and 60 minutes.

Select the alias name of the Integration Cloud trust store configuration. The trust store contains trusted certificates used to determine trust for the remote server peer certificates. You can also add a new Truststore from this field.

Select this option if you want to enable connection pooling for a connection.

Integration Cloud includes a connection management service that dynamically manages connections and connection pools based on configuration settings that you specify for the connection. A connection pool is a collection of connections with the same set of attributes. Connection pools improve performance by enabling Integrations to reuse open connections instead of opening new connections for every service request.

When you enable connection pooling, Integration Cloud creates the number of connection instances you specified in the connection's Minimum Pool Size field. Whenever an Integration needs a connection, Integration Cloud provides a connection from the pool. If no connections are available in the pool, and the Maximum Pool Size has not been reached, Integration Cloud creates one or more new connections (according to the number specified in the Pool Increment Size field) and adds them to the connection pool.

If the pool is full (as specified in the Maximum Pool Size field), the requesting service will wait for Integration Cloud to obtain a connection till one sec, until a connection becomes available. Periodically, Integration Cloud inspects the pool and removes inactive connections that have exceeded the expiration period of one sec.

The minimum number of connection objects that remain in the connection pool at all times, if connection pooling is enabled. When the connector creates the pool, it creates this number of connections.

The maximum number of connection objects that can exist in the connection pool if connection pooling is enabled. When the connection pool has reached its maximum number of connections, the connector will reuse any inactive connections in the pool, or, if all connections are active, it will wait for a connection to become available.

The number of connections by which the pool will be incremented, up to the maximum pool size, if connection pooling is enabled and connections are needed.

Select a hostname verifier implementation. Guards against man-in-the-middle (MITM) attacks. The default is org.apache.http.conn.ssl.DefaultHostnameVerifier, which will enable hostname verification. Select org.apache.http.conn.ssl.NoopHostnameVerifier to disable hostname verification.

The keep alive interval in milliseconds defines the interval for which a connection will be kept alive, if the back end does not respond with a Keep-Alive header. A value > 0 keeps the connection alive for the specified value. The default value of -1 implies that the connection will be kept alive until a request fails due to a connection error.

The idle timeout interval in milliseconds defines the interval for which a connection will be kept alive if it's not in use. A value > 0 keeps the connection alive for the specified value. The default value of -1 implies that the connection will be kept alive until a request fails due to a connection error.

Select the alias for the Integration Cloud key store configuration. This is a text identifier for the keystore alias. A keystore file contains the credentials (private key/signed certificate) that a client needs for authentication. You can also add a new Keystore from this field.

Alias to the private key in the keystore file specified in the Keystore Alias field. The outbound connections use this key to send client credentials to a remote server. To send the client’s identity to a remote server, you must specify values in both the Keystore Alias and the Client Key Alias fields.

The number of milliseconds a connection waits before canceling its attempt to connect to the resource. If you specify 0, the connection waits indefinitely. It is recommended that you specify a value other than 0 to avoid using a socket with no timeout.

The number of times the system should attempt to initialize the connection at startup if the initial attempt fails.

The system retries to establish a connection when an I/O error occurs while sending the request message to the back end. If an I/O exception occurs when the system is reading a response back from the back end, the system will only retry if Retry on Response Failure is enabled.

Server Name Indication (SNI) is an extension to the TLS protocol by which a client indicates which host name it is attempting to connect to at the start of the handshaking process. Enable this option if the SaaS provider offers SNI-based TLS connectivity, and if you want to connect to an SNI enabled SAAS provider to send the host name specified in the Server URL field, as part of the TLS SNI Extension server_name parameter.

If you want to explicitly specify a host name to be included as a part of the SNI extension server_name parameter, in case the host name is other than the host name specified in the Server URL field, specify the host name value in the SNI Server Name field.

Enable this option if you want to send or receive a large binary stream with a chunk size of 8192 bytes. This is applicable only if the back end supports HTTP/1.1 chunking.