Auth0 with OpenID SSO

Connect Auth0 to Document360 with OpenID Connect (OIDC) so your users and readers sign in to Document360 with their existing Auth0 credentials instead of separate Document360 passwords. You create a web application in Auth0, exchange the redirect URIs and client values with Document360, and create the SSO configuration. When you finish, your users sign in to the knowledge base portal and your readers sign in to the knowledge base site through Auth0.

When to use Auth0 with OpenID Connect

Use this setup when:

• Your organization manages identities in Auth0.
• You want users and readers to sign in with one set of Auth0 credentials and want central control of who can access Document360.
• You plan to add and manage SSO users and readers in Document360 yourself.

With Auth0 as your OpenID Connect identity provider (IdP), you can use the following:

Before you begin

• You have the Owner or Admin project role in Document360. Only these roles can configure SSO.
• You have an active Auth0 account. If you need one, sign up at auth0.com/signup.
• Open Document360 and Auth0 in two separate browser tabs. You switch between them several times during setup.

How to set up OpenID Connect SSO with Auth0

Step 1: Create an application in Auth0

1. Log in to your Auth0 account and find the Applications menu in the left navigation.
2. Click Applications > Create Application.
3. Enter a name for your application and select Regular Web Applications as the application type.
4. Click Create.

Leave the Auth0 tab open while you get the values from Document360.

Step 2: Get the service provider parameters from Document360

1. In the Document360 tab, go to Settings () > Users & Permissions > Enterprise SSO.
2. Click Create SSO, and then select OpenID Connect (Modern SSO using OpenID Connect (OIDC)).

3. On the Choose IdP step, select Others as your identity provider. Auth0 isn't listed as a separate option.

The Configure SP step opens and shows the parameters you need in Auth0.

Step 3: Enter the Document360 parameters in Auth0

1. Switch to the Auth0 tab and open your application's settings.
2. Copy each Document360 value into the matching Auth0 field. Paste the Sign-in redirect URI into both Auth0 fields listed.

3. Click Save changes at the bottom of the page.

Auth0 saves the redirect URIs for your application.

Step 4: Configure the identity provider in Document360

1. Return to the Document360 tab and click Next on the Configure SP step.

The Configure IdP step opens.

2. Copy each value from your Auth0 application into the matching Document360 field. In Auth0, these values are on the application's Settings tab under Basic Information.

3. (Optional) In the Scope field, type a scope value and click + to add it as a chip. Scopes define what user information Document360 requests from Auth0. You can add up to 3 scopes.
4. Click Next.

Step 5: Configure more settings and create the configuration

1. In the SSO name field, enter a name for the SSO configuration.
2. In the Login button text field, enter the text for the sign-in button. If you leave the default, the button reads Login with SSO.
3. (Optional) Turn on Idle session SSO timeout and set the Timeout duration (HH:MM) after which Document360 signs out an idle SSO user.
4. (Optional) To move existing accounts to SSO now, turn on Convert existing team and reader accounts to SSO. Then, under Send invite to, select All users or Selected users.

5. Click Create.

Document360 creates the OpenID Connect SSO configuration with Auth0 and lists it on the Enterprise SSO page.

Step 6: Test the sign-in

1. Open the Document360 sign-in page in a private browser window.
2. Enter your email or subdomain and click Login with SSO (or the custom button text you set in Step 5).
3. Sign in with an Auth0 account.

Auth0 redirects you back to Document360 and you are signed in. If sign-in fails, see OpenID SSO issues.

Considerations

Best practices

• Use the Domain value for Authority. Auth0 provides a Domain field in your application settings. This maps to the Authority field in Document360, not an Issuer URI or full URL.
• Paste the Sign-in redirect URI in both fields. Enter it in both Application Login URI and Allowed Callback URLs in Auth0. Missing either field causes sign-in failures.
• Test with a single user first. Complete Step 6 with one test account to confirm the Client ID, Client Secret, Domain, and redirect URIs before you convert existing accounts.
• Keep the default login page until SSO works. Disable it only after you confirm sign-in. See Deactivating Document360 login page.

Related articles

• Sign out idle SSO user
• Mapping an existing SSO configuration to other projects
• Log in using SSO - Knowledge base portal

FAQ