Auth Configurations

The Auth Configs section of the StackOne dashboard allows you to manage connectors for a StackOne Project. On the Connectors page, you can:

• View the list of all connectors for all the categories supported by StackOne (e.g., HRIS, ATS, IAM, CRM, Marketing, LMS, and more). Some connectors and categories are only available based on your plan or contract. If you do not see a category or connector that you would like, contact your support manager.
• Enable, configure, and disable connectors.
• Quickly access linked accounts and logs related to the connectors
• Delete auth configurations

​

Configuring your first connector

To configure your first connector, navigate to the Connectors section and click on the + button. You will be presented with a list of connectors to choose from. Select the connector you want to configure. You can also search for a specific connector by name. Once you have selected the connector, you will be presented with a form to configure the auth settings. Fill in the form with the required information and click the Save button. You will notice a “Default Configuration” dropdown that allows you to mark an auth config as the default configuration for that connector in the project. You can change the default configuration later once you have configured multiple auth configs for the same connector. Once you have configured the connector, you will see it in the list of connectors.

​

Managing connectors

​

Enabling and disabling connectors

Setting up a connector for the first time will automatically set its state as enabled, meaning it will be displayed in the StackOne Hub and you will be able to retrieve a Connect Session token with the associated provider key. When disabling a connector, a warning will appear. Note that disabling a connector with linked accounts will make all those accounts go into an inactive status, and API requests to these accounts will not be permitted. You can switch any connector back to an enabled state just as easily, which will reset all associated linked accounts to an active status.

​

Ellipsis menu options

The ellipsis menu on each connector row provides the following options:

• Edit - Modify the auth configuration
• View logs - See logs for this connector
• Copy connector ID - Copy identifiers for API use
• Disable - Temporarily disable the connector
• Delete - Remove the auth config (only available if no linked accounts exist and it’s not the sole default)
• Make default - Set as the default auth config for this connector (only shown for non-default configs when multiple exist)

​

Deleting an auth config

You’ll only be able to delete an auth config if there are no linked accounts for it, and if it’s either the only config for the connector or a non-default config for the connector.

​

Authentication types

When setting up or updating a connector, you are configuring a specific authentication type. The authentication type determines the process for your end-user to link their account for that provider, specifically which details or credentials they will need to submit.

​

API Key and Basic Token

In most instances, you will see API Key or Basic Token, in which case the end-user will need to generate the required secret (e.g., Ashby or Hibob).

​

OAuth-based authentications

For other connectors, you may have a choice of OAuth (and similar, e.g., OIDC), in which case your user may experience a simpler login-like flow (e.g., Lever or Hubspot). Some connectors will prompt for OAuth-based fields such as Client ID and Client Secret. You can use StackOne-provided secrets, but your end-users may see StackOne branding when linking accounts. To use your own OAuth or partner credentials, contact StackOne support for assistance.

​

Configuring multiple auth configs for the same connector

You can configure multiple auth configs for the same connector. This is useful if you want to use different configurations for the same connector for different groups of accounts in the same project, for example if some accounts need to be linked with an API key and others with an OAuth token. To configure multiple auth configs for the same connector, you can go to the Connectors page and click on the + button. You will be presented with the same form as before, and you will be able to configure whether this auth config should be the default for the connector or not. You can toggle the default auth config for the connector by clicking on the “Make default” option mentioned in the ellipsis menu options section above. For example, with the Airtable connector we used in the previous example, we previously set up an API Key auth config. Now we want to set up an OAuth 2.0 auth config. If we set the API Key auth config as the default, in the hub we’ll show the API Key setup fields. In this case, the difference between the two is the OAuth authorization flow. However, if we set the OAuth 2.0 auth config as the default, in the hub we’ll show the OAuth 2.0 setup fields. Notice the different authentication flow presented to users. You will be able to select which specific auth config to use in the hub in the future without having to toggle the default for the connector back and forth.

​

Troubleshooting