DokLocker + Okta integration

What the Okta integration does

Each client's users, licenses and managed devices sit next to the rest of their documentation, refreshed automatically.

Setting it up

The Okta and other single sign-on card works with any OpenID Connect provider: Okta, Microsoft Entra ID (limited to your own tenant), Google Workspace, JumpCloud, Duo, OneLogin, Auth0, Keycloak and Authentik.

1. In your provider, create a web application that uses OpenID Connect with the authorization code flow. Give it the scopes openid, email and profile.
2. Paste the redirect address shown on the card into the app's sign-in redirect URIs.
3. Assign the app to the people who use DokLocker.
4. Back in DokLocker, fill in:
5. Button name: what the sign-in button says, for example Okta.
6. Issuer URL: for Okta https://yourcompany.okta.com; for Entra ID https://login.microsoftonline.com/<your tenant ID>/v2.0; for Google https://accounts.google.com; for JumpCloud https://oauth.id.jumpcloud.com/.
7. Client ID and Client secret from the app.
8. Click Save, then Test connection. DokLocker checks that it can reach your provider.

The sign-in page then shows Sign in with Okta (or your button name). It only lets in people who already have a DokLocker account with the same email; new people still need an invitation. To make everyone use it, turn on Sign in only with Google, Microsoft or single sign-on under Admin › Security.

Included in every plan

Every integration is included at no extra cost, on the hosted service and self-hosted. Connect it under Admin › Integrations, click Test, and the first sync starts straight away.

More Cloud and identity integrations

See all integrations