Skip to main content
All CollectionsSingle Sign-on (SSO)
Using Single Sign-on (SSO)
Using Single Sign-on (SSO)

Configuring your Identity Provider to sign-in to Enterpret

Team Enterpret avatar
Written by Team Enterpret
Updated over a week ago

SSO on Enterpret

Enterpret enables you to sign in using Single Sign-on (SSO). You can enable SSO sign-in as an option on Enterpret by connecting your identity provider. Enterpret is compatible with any identity provider that supports OpenID. In this article, we'll go through a step-by-step guide to enable SSO for your organisation.

Configuring SSO

NOTE: To follow this guide, you must have Admin access on Enterpret and the required access in your Identity Provider.

Configuring your Identity Provider

Please follow the following instructions to configure your identity provider and generate the client ID, client secret and issuer URL.

If you use a different identity provider or are facing configuration issues, please get in touch with the Enterpret team, and we'll be happy to help!

Configuring SSO on Enterpret

Navigate to admin settings from the left-bottom menu option

Click on the Configure button.

Upon being prompted, provide the clientID, clientSecret and issuerURL values that you copied while configuring your identity provider. and click submit.

And that's it! SSO sign-in should not be configured for your account. You can log out and attempt to log back in via SSO.

Enforcing SSO

If you want all users from your organisation to compulsorily authenticate via SSO, you can toggle the Enforce SSO setting. This would make ensure that any user who accesses your organisation's Enterpret instance authenticates via your configured identity provider.

NOTE: Please ensure that SSO sign-in is working before enforcing SSO to avoid losing access to your Enterpret instance.

If you encounter any issues, please reach out to the Enterpret team, we'll be happy to help!

Setting Up User De-provisioning

You can configure SSO to automatically de-provision users who've been deactivated or removed from your organisation's SSO identity provider.

Currently, user de-provisioning is supported for Okta. If you use a different identity provider or are facing configuration issues, please feel free to reach out!

Did this answer your question?