Introduction

Connected systems allow designers to manage authentication details for multiple integrations in one place. There are several authentication options available for connected systems.

• To learn about connected system objects and their configuration options, see Connected System Object.
• To learn how to create a connected system, see Create a Connected System.
• To learn how to use different types of connected systems to connect to different systems, see Connected Systems.
• To learn how to use a connected system when creating an integration, see Create an Integration.
• For a real-world example of how to to build and use connected systems and integrations, see the Integration Tutorial.

Authentication Types

None

No specific authentication will be applied. You can provide custom authentication values in the integration's URL, parameters, or headers as required by the external system. Client certificate/mutual SSL authentication can be enabled by uploading client certificates in the Admin Console. Services that use self-signed or internal SSL certificates can be enabled by uploading trusted server certificates in the Admin Console.

API Key Properties

Although API keys can be configured directly in the integration headers or parameters, the only way to securely configure an API key for an integration is by using the connected system object. The following properties are available for configuration when API key is selected as the authentication type:

Field	Description
Send As	Required. This field specifies whether the API key should be sent as an http header or a query parameter.
Header/Parameter Name	Required. The key identifier of the API key.
Value	Required. The key value of the API key. This value is masked to prevent unauthorized users from seeing and should be treated as a password.

AWS Signature Version 4

To see the configurable properties for this authentication type, see AWS Signature Version 4 Authentication

Basic Authentication Properties

The following properties are available for configuration when Basic Authentication is selected as the authentication type:

Field	Description
Username	Optional. The username to use for authentication. This value is encrypted and supports environment specific configuration.
Password	Optional. The password to use for authentication. This value is masked, encrypted and supports environment specific configuration.
Send credentials preemptively instead of waiting for a 401 authentication challenge	Optional. Determines whether or not authentication credentials are sent only after a 401 Not Authorized response or, when selected, before the system has challenged.

Google Service Account Properties

To see the configurable properties for this authentication type, see Google Service Account Authentication.

OAuth 2.0: Authorization Code Grant Properties

To see the configurable properties for this authentication type, see OAuth 2.0: Authorization Code Grant.

OAuth 2.0: Client Credentials Grant Properties

To see the configurable properties for this authentication type, see OAuth 2.0: Client Credentials Grant.