This is the login endpoint to initiate communication with the SaaS provider.

Specify the URL for your exact instance, for example: https://<instance>.workday.com/ccx/service/<tenantID>/.

For example, wd2-impl-services1 is the instance and softwareag_pt1 is the tenantID.

User name for the Workday tenant to log in to Workday. Enter the user name appended with the Workday Tenant ID, for example, username@tenantID.

The password of the Workday account.

The type of HTTP authorization scheme to use for the connection. If you select none, no additional authorization scheme will be executed at run time.

If you specify a Username and Password and also select none, you do not specify a value for the Authorization Type, so the user credentials are not inserted into an Authorization header. If you enter the Username and Password, then set the authorization type as basic.

Basic refers to HTTP Basic Authentication. This option can be used if the Application requires or supports HTTP Basic authentication using a username and password. If you enter the username and password, then set the authorization type as basic.

The Workday instance, for example, wd2-impl-services1.

The Workday tenant ID that you want to access, for example, softwareag_pt1.

SOAP API version of Workday. The version value is obtained from the soapbind:address location in the WSDL file. For example, if the soapbind:address location is https://wd2-impl-services1.workday.com/ccx/service/softwareag_pt1/Staffing/v31.1, then the version is v31.1.

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.

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.

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 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.

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.