SSO Setup
Antidote uses WorkOS to provide authentication so that we can provide easy single sign-on setup for a wide range of identity providers.
Admin user
Provide us with the email address of an administrator who has access to configure a new application in your SAML provider and has an email address within the domain being added. They will receive an email from Antidote's WorkOS account.
Following the link will provide either two options, if your domain needs verification, or one option to configure SSO if the domain has already been verified separately.
Antidote will add your principal domain and other domains that are provably yours to your organization. In the rare cases we need domain verification, see DNS Domain Verification.
SSO Setup
To set up SSO select or search your identity provider from the list. A list of all providers and setup instructions is also available in the WorkOS integration guides here.
Follow the instructions for your provider. When complete you will be asked to complete a test sign on.
This test sign on must be completed for the connection to be created. If the person setting up the connection does not have an email login for the domain the organization is being configured with, they must obtain test credentials for that domain in order to complete this step.
Antidote will receive an email when the connection is complete, so we can confirm this with you.
Multiple Domains
Setup depends on whether you have a single instance of Antidote, or separate instances for different organizations.
Single Instance of Antidote
For a single instance, which is the most common case, you need to provide us with all of the email domains that belong to you and that users may use to log in, so that we can associate them all with your organization. If this is not done, users may be prevented from logging in even if the SSO connection is valid.
More than one instance of Antidote
If there is more than one Antidote instance, either all users can authenticate to a primary organization first, with a subset of users then added on request by Antidote to the second organization. This requires only one SSO connection to be established. If instead users need to be divided between the organizations based on login email, the SSO connection must return the correct email domain associated with the organization the user is placed into, and if the connections are within the same Entra ID instance, multiple apps must be created that map to each organization.
Multiple organizations require planning — contact support or your customer success manager to agree a configuration and roll-out plan.