Acceldata
ADOC

Last updated: Nov 14, 2026 05:37 UTC

Single Sign-On

Single Sign-On (SSO) lets users sign in to ADOC with your organization’s identity provider (IdP), such as Okta or Microsoft Entra ID, instead of a separate ADOC user name and password.

You can set up SSO with SAML or OpenID Connect (OIDC), sync users from an LDAP directory, and provision users and groups with SCIM.

Access SSO settings

  1. In the left navigation, select Control Center > Security > SSO Authentication.

The SSO Authentication page lists each provider with its type and status:

  • Authentication Providers: SAML and OpenID Connect. Use these to sign users in with your IdP.
  • User Federations: LDAP. Use this to sync user accounts from an external directory.

To hide the user name and password form on the sign-in page so that users can sign in only with SSO, turn on Hide credentials login.

SSO Authentication Options

Prerequisites for SSO Authentication

Before configuring SAML or OpenID Connect (OIDC) in ADOC, make sure that your organization has a supported Identity Provider (IdP) (such as Okta, Azure AD, Ping Identity, or other SAML/OIDC-compliant systems) set up and managing user authentication.

  • For SAML, your IdP must be able to provide a valid metadata XML file and endpoints for Single Sign-On and Authentication.
  • For OIDC, your IdP must support OAuth 2.0 flows and provide client credentials (Client ID and Client Secret), token claims, and metadata endpoints.
  • You have administrator access in your IdP to register ADOC as an application.

You can set up SSO in ADOC using two industry-standard methods:

1. SAML (Security Assertion Markup Language)

  • Lets users sign in to multiple applications with one set of credentials.

Example: You sign in to your company’s Okta portal, and ADOC signs you in automatically.

To configure SAML:

  • On the SSO Authentication page, select SAML.
  • In Browse XML, select Choose File, and then select the SAML metadata XML file from your IdP. ADOC fills in Single Sign On URL from the file.
  • Copy the Auth URL, and add it to your IdP as the Reply URL (Assertion Consumer Service).
  • Optionally, turn on Enable user group sync to add users to ADOC groups when they sign in. For more information, see Assign users to groups automatically.
  • Select Save.

Service Provider (SP) Details for Your Identity Provider

When registering ADOC as a Service Provider in Azure AD (or another SAML-compliant IdP), your IdP administrator needs the following ADOC endpoint and attribute details to complete the trust configuration:

Parameter

Value

Identifier (Entity ID)

https://accounts.acceldata.app/auth/realms/<tenant-realm>

Reply URL (Assertion Consumer Service)

https://accounts.acceldata.app/auth/realms/<tenant-realm>/broker/saml/endpoint/clients/saml

Logout URL

https://accounts.acceldata.app/auth/realms/<tenant-realm>/broker/saml/endpoint/clients/saml

Name ID Format

urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified

Replace <tenant-realm> with your ADOC tenant's realm name.

Attribute & Claims Mapping

Configure your IdP to send the following user attributes in the SAML assertion:

Attribute

Description

firstName

User's first name

lastName

User's last name

email

User's email address — required if SCIM provisioning is also enabled

[Group attribute name: confirm with engineering]

The groups the user belongs to in your IdP. Required only if you turn on Enable user group sync.

  • ADOC functions as the Service Provider (SP); your IdP functions as the Identity Provider (IdP).
  • Signed AuthnRequests and Assertions are not required.

Assign users to groups automatically

When you turn on Enable user group sync, ADOC reads the user’s groups from the SAML assertion each time the user signs in. ADOC adds the user to the ADOC groups that have the same names, and the user gets the roles and domain access of those groups. You don’t need SCIM provisioning.

Changes to a user’s groups in your IdP take effect the next time the user signs in to ADOC. Group sync doesn’t change groups that SCIM manages. If Allow create user groups is turned off, ADOC ignores IdP groups that don’t have a matching ADOC group.

ADOC has two kinds of user groups: normal user groups, which an administrator creates in ADOC, and SSO user groups, which ADOC creates during group sync.

Before you begin, configure your IdP to send the user’s groups in the SAML assertion. For more information, see Attribute & Claims Mapping.

To turn on group sync:

  1. In the left navigation, select Control Center > Security > SSO Authentication, and then select SAML.
  2. Turn on Enable user group sync.
  3. Turn on the group sync options that you need. For more information, see the following list.
  4. Select Save.

Group sync options:

  • Allow create user groups: Creates the group in ADOC as an SSO user group when the IdP sends a group that doesn’t exist in ADOC.
  • Allow add users to normal groups: Adds the user to a normal user group when the IdP sends that group’s name. Turn on this option to add users to groups that you created in ADOC.
  • Allow remove users from SSO groups: Removes the user from an SSO user group when the IdP no longer sends that group. Normal user groups don’t change.
  • Allow remove users from normal groups: Removes the user from a normal user group when the IdP doesn’t send that group. SSO user groups don’t change.
  • Fail login on sync error: Blocks the user from signing in if group sync fails.

2. OpenID Connect (OIDC)

Built on top of OAuth 2.0, OIDC adds identity verification on top of secure token-based access.

Example: You log into your Microsoft or Google account, and ADOC recognizes you and signs you in.

Redirect URI for your identity provider

Before you can get a Client ID and Client Secret from your identity provider, you need to register ADOC as an application in it — and every IdP asks for a redirect URI as part of that registration.

From the OIDC configuration page in ADOC, copy the Sign In & Out Redirect URL shown at the top of the page. It's specific to your ADOC tenant and looks like:

https://accounts.acceldata.app/auth/realms/<tenant>/broker/oidc/endpoint

Enter this as the redirect (or callback) URI when you register the application in your identity provider. Your IdP then gives you back the Client ID and Client Secret you'll need for Step 1 below.

Setup steps

Configuring OIDC in ADOC has five steps.

Step 1: OIDC Credentials

Enter the Client ID and Client Secret from your identity provider's application configuration — the credentials you received after registering ADOC using the redirect URI above.

Field

Description

Client ID

The identifier your IdP assigned to the ADOC application when you registered it.

Client Secret

The confidential secret your IdP issued alongside the Client ID. Treat this like a password.

Step 2: OIDC Provider Metadata (optional)

Most identity providers publish a metadata document that lists their OIDC endpoints in one place. If you provide it, ADOC uses it to fill in the Authorization, Token, and Logout endpoints for you automatically.

Field

Description

Provider Metadata Endpoint

Your IdP's OpenID configuration URL, typically ending in /.well-known/openid-configuration.

If you don't have this URL, or your IdP doesn't publish one, skip this step and enter the endpoints manually in Step 3.

Step 3: Endpoints & Claims

If you skipped Step 2, enter each endpoint manually here. If you provided a metadata URL, review the auto-filled values.

Field

Description

Authorization Endpoint

Where ADOC redirects users to log in and grant consent.

Token Endpoint

Where ADOC exchanges an authorization code for an access token.

Logout Endpoint

Where ADOC sends users to sign out of your IdP as well as ADOC.

UserInfo Endpoint (optional)

Where ADOC retrieves additional user profile details after authentication, if your IdP's access token doesn't already include them.

Access Token is JWT — Turn this on if your IdP's access token is itself a JWT that ADOC can read claims from directly. Turn it off if your IdP issues an opaque access token, so ADOC instead calls the UserInfo endpoint to retrieve claims. [Placeholder: confirm this behavior against the in-product tooltip before publishing — the field has an info icon whose exact wording I don't have.]

Token Claim Mapping — Map ADOC's user attributes to the claim names your IdP's token actually uses. The defaults below follow the standard OIDC claim names; change them only if your IdP uses non-standard names.

ADOC Attribute

Default Token Claim

Email

email

First Name

given_name

Last Name

family_name

Step 4: Additional Information (optional)

Field

Description

Identity Provider Name (optional)

A display name for this OIDC provider, useful if you configure more than one. Defaults to oidc.

Step 5: Review Configuration

Review every value entered in Steps 1–4 — Client ID, Client Secret (masked), Redirect URI, each endpoint, Identity Provider Name, and the token claim mappings — then select Save.

User Federations (Syncing Users)

User federations connect ADOC to external directories, so you don’t have to manually add or update users.

LDAP (Lightweight Directory Access Protocol)

Used to pull in users from your company’s existing directory service.

Example: If a new employee is added in your corporate directory, they’ll automatically appear in ADOC after sync.

Setup basics:

  1. From the SSO Authentication page, click LDAP.
  2. From the LDAP page, enter the following LDAP server details: URL, Distinguished Names (DNs), Bind credentials, and attribute mappings (username, unique ID, etc.).
  3. Test the connection and save.

Provisioning (SCIM)

Provisioning automates user and group creation in ADOC from your identity provider (IdP).

Example: HR adds a new employee to Okta → they instantly get an ADOC account with the right roles.

Setup basics:

  1. In the left navigation, select Control Center > Security > Provisioning.
  2. From the Provisioning page, enable SCIM (System for Cross-domain Identity Management).
  3. Copy the SCIM URL and token into your IdP’s provisioning configuration.
  4. Test and save.

Groups managed by SCIM can’t have their roles edited directly in ADOC. To change roles, update them in the IdP.

Warning

Important

ADOC uses a user's email address as the unique identifier for SCIM provisioning. If your identity provider later sends an updated email for an existing user (for example, after a name change), ADOC does not rename the existing account — it creates a new one instead, which can result in duplicate accounts for the same person. Because most identity providers treat an email change as an update rather than a new-user event, the newly created account typically won't receive its expected group memberships automatically. To avoid this, standardize the email format used for SCIM provisioning across your organization before you begin, and limit your SCIM attribute mappings to only the required fields. If duplicates do occur, either assign the correct groups to the new account manually, or delete it and re-run SCIM provisioning to recreate it with the correct identity and group memberships.

Assigning Roles to SCIM-Managed Groups

  1. On the Provisioning page, in the groups table, select the Edit icon for the group.
  2. Provide a name and description for the group.
  3. Select the required roles for the group.
  4. Select domains and map them to required roles. Use the + Add More button to map additional domains and roles.
  5. Click Update to save your changes.