Multiple Authentication Support for V2 Systems

Overview

Multiple Authentication Support allows a single system version to support multiple authentication methods.

Previously, a system version could only support one authentication method, requiring users to connect using that specific authentication type. With this enhancement, System Builders can configure multiple authentication types for a single system version, allowing System Users to choose the method that best fits their environment.

Example: A Magento system can support both OAuth 1 and Bearer Token authentication within the same published version.

Benefits

  • Support multiple authentication methods within a single system version.
  • Allow users to choose their preferred authentication method.
  • Maintain separate credentials for different authentication types.
  • Reduce the need for duplicate system versions.
  • Validate authentication compatibility during version upgrades and downgrades.
  • Preserve compatibility with existing single-authentication systems.

Core Concepts

TermDescription
Authentication TypeThe method used to authenticate with an external system, such as OAuth 1 or Bearer Token.
Default Authentication TypeThe authentication type selected automatically when creating credentials.
Credential InputsAuthentication-specific fields required to Addcreate a credential.
API Common FieldsAuthentication-specific headers and parameters applied to API requests.

How It Works

  1. A System Builder configures one or more authentication types for a system version.
  2. A default authentication type is selected.
  3. Credential Inputs and API Common Fields are configured for each authentication type.
  4. The system version is published.
  5. Users create credentials using a supported authentication type.
  6. The system displays the fields required for the selected authentication type.
  7. Users test and save their credentials.

Key Features

Multiple Authentication Types

V2 System Revamp Admin Coordinated Universal Time ? LOG S Shopify with 2 Authentications Private Save draft Basic DetailsAuthenticationTest ConnectionAPI ManagerOther Versions No Authentication Basic Authentication Basic Authentication Uses a username and password, sent with each request to access the system. Default Credential Fields Host name InputCommon Keyhost_name Override Valuehttps://test.myshopify.com RequiredRequired Add Credential Fields Builder Credential One test account for this authentication, used only while building. Never shared with projects. Add Authentication Each authentication gets its own credential fields. Methods already added are marked. No AuthenticationThe system doesn’t require credentials toaccess the resource. Static tokens like bearertokens can be used if needed.Added Basic AuthenticationUses a username and password, sent with eachrequest to access the system.Added Dynamic Token AuthenticationGets access tokens through one or more token endpoints.Manually add them to API headers or parameters. OAuth 1.0A legacy protocol uses signed requests with consumerkeys and secrets. OAuth 2.0A widely adopted protocol that provides secure, token-based authentication and authorization.

A single system version can support multiple authentication methods, allowing different users to connect using the authentication method that best fits their requirements.

Authentication Selection

Users can choose from the authentication methods configured for the system version. The default authentication type is selected automatically but can be changed if other options are available.

Authentication-Specific Credential Inputs

V2 System Revamp Admin Coordinated Universal Time ? LOG Basic DetailsAuthentication •Test ConnectionAPI ManagerOther Versions No Authentication Basic Authentication Default Add authentication Basic Authentication Uses a username and password, sent with each request to access the system. Default Credential Fields Host name InputCommon Keyhost_name Override Valuehttps://test.myshopify.com RequiredRequired Add Credential Fields Builder Credential One test account for this authentication, used only while building. Never shared with projects. Test Basic Auth 3 Successful Test connection API Common Fields

Credential forms dynamically update based on the selected authentication type, displaying only the fields required for that method.

Multiple Credentials

Users can create and manage separate credentials for different authentication methods within the same system version.

Authentication-Specific API Configuration

Host name InputCommon Keyhost_name Override Valuehttps://test.myshopify.com RequiredRequired Add Credential Fields Builder Credential One test account for this authentication, used only while building. Never shared with projects. Test Basic Auth 3 Successful Test connection API Common Fields Headers and parameters added to every API that uses this authentication. KEYVALUESENT IN Content-Type application/json Header Edit common fields V2 System Revamp Admin Coordinated Universal Time ? LOG

API Common Fields can be configured separately for each authentication type, ensuring the correct authentication-related headers and parameters are applied automatically.

Version Compatibility Validation

During system upgrades or downgrades, credentials are validated against the authentication methods supported by the target version.

Getting Started

System Builders

  1. Configure one or more authentication types.
  2. Select a default authentication type.
  3. Configure Credential Inputs and API Common Fields for each authentication type.
  4. Publish the system version.

System Users

  1. Create a credential for the published system.
  2. Select a supported authentication type.
  3. Enter the required authentication details.
  4. Test and save the credential.
  5. Use the credential in your integrations and workflows.

Note: If multiple authentication types are available, separate credentials can be created for each supported authentication method.

Version Upgrade and Downgrade Behavior

ScenarioOutcome
Authentication type is supported in the target versionCredential remains valid.
Authentication type is not supported in the target versionCredential becomes invalid and the user is prompted to create a supported credential.
Only some authentication types are unsupportedOnly the affected credentials become invalid.
Existing synchronizationsContinue to operate without interruption.

Important Notes

  • A maximum of one Builder Credential can be configured per authentication type.
  • Builder Credentials are not exposed to System Users.
  • Existing single-authentication systems continue to function without changes.
  • Multiple Authentication Support is available only for V2 Systems.
  • Existing workflows are not modified solely to support multiple authentication methods.

Troubleshooting

IssueResolution
Unable to save a credentialComplete all mandatory fields for the selected authentication type.
Test Connection failsVerify the credential values and test again.
Unable to create another Builder CredentialOnly one Builder Credential is allowed per authentication type.
Credential becomes invalid after a version changeCreate a new credential using a supported authentication type.
Expected authentication type is not availableVerify the supported authentication types configured for the system version.

Frequently Asked Questions

Can a single system version support multiple authentication methods?
 Yes. A system version can support multiple authentication types simultaneously.

Can I create multiple credentials for the same system?
 Yes. Separate credentials can be created for different supported authentication types.

Can I create multiple Builder Credentials for the same authentication type?
 No. Only one Builder Credential is allowed per authentication type.

What happens if my authentication type is no longer supported after a version upgrade?
 The credential becomes invalid for that version, and you will be prompted to create a credential using a supported authentication type.

Will existing synchronizations stop working after a version change?
 No. Existing synchronizations continue to operate without interruption.

Glossary

TermDescription
Authentication TypeA method used to verify access to an external system, such as OAuth 1 or Bearer Token.
Default Authentication TypeThe authentication method selected automatically when creating a credential.
CredentialAuthentication information used to connect to a system.
Credential InputsThe fields required to create a credential for a specific authentication type.
API Common FieldsShared headers and parameters automatically applied to API requests for a specific authentication type.
Builder CredentialA credential configured by a System Builder for a specific authentication type.
System BuilderA user who configures and publishes system versions.
System UserA user who creates credentials and uses systems in integrations and workflows.
Test ConnectionA validation check used to verify that a credential can successfully connect to a system.