Overview

Arist's application supports Single Sign-On (SSO), allowing employees to access it using their workplace credentials. This eliminates the need for separate Arist account creation. We leverage Auth0 by Okta for seamless SSO integration.

Supported Enterprise Identity Providers:

• Okta

• Active Directory/LDAP

• ADFS

• Azure Active Directory (Native & Standard)

• Google Workspace

• OpenID Connect

• PingFederate

• SAML

Integration Steps for Each Identity Provider

1. Okta:

   • Client's Role: Provide Connection Name (no spaces), Okta Domain, Client ID, and Client Secret.

   • Setup: Arist configures an Enterprise connection in Auth0 for the client.

   • Testing: Client's IT team installs the connector and verifies the connection.

2. Active Directory/LDAP:

   • Client's Role: Provide Connection Name (no spaces), Display Name, Logo URL, IdP Domains, and other optional settings.

   • Setup: Arist establishes an Enterprise connection in Auth0.

   • Testing: Post-installation, the client's IT team conducts connection validation.

3. ADFS:

   • Client's Role: Implement the provided Realm Identifier and Endpoint script.

   • Setup: Arist initiates the Enterprise connection in Auth0.

   • Testing: Connection validation by the client’s IT team.

4. Azure Active Directory Native:

   • Client's Role: Grant API access to Arist.

   • Setup: Arist creates an Enterprise connection in Auth0.

   • Testing: Connection is tested and validated by the client's IT team.

5. Google Workspace:

   • Client's Role: Provide Connection Name (no spaces), Google Workspace Domain, Client ID, Client Secret, and attribute settings.

   • Setup: Arist sets up the connection in the client’s Google Workspace.

   • Testing: Connection is tested and validated by the client's IT team.

6. OpenID Connect:

   • Client's Role: Provide Connection Name (no spaces), Issuer URL, Client ID, and Callback URL.

   • Setup: Arist establishes the Enterprise connection in Auth0.

   • Testing: Client's OpenID Admin tests and validates the connection.

7. PingFederate:

   • Client's Role: Provide the Base64 encoded signing certificate.

   • Testing: Connection tested and validated by the client's IT team.

8. SAML:

   • Client's Role: Provide Connection Name (no spaces), Sign In URL, X.509 Signing Certificate, and other optional settings.

   • Setup: Arist creates an Enterprise connection in Auth0.

   • Testing: Connection tested and validated by the client's IT team.

For detailed technical specifications and additional support, refer to this detailed Auth0 documentation or contact our technical support team at support@arist.co with additional requests.