Skip to main content
All CollectionsI'm an administrator Getting started
How to use Credentially Single Sign-On (SSO)
How to use Credentially Single Sign-On (SSO)
Irina Zadrutskaya avatar
Written by Irina Zadrutskaya
Updated over 2 years ago


If your company already uses Single Sign-On (SSO), the following guide will get you on the path to linking Credentially and easing the management of various usernames and passwords for our software.


What Is SSO?

Single Sign-On (SSO) is a session and user authentication service that permits a user to use one set of login credentials (e.g. a name and password) to access multiple applications. With the connected SSO on Credentially, users can sign up to the system in a few clicks with one of the following default SSO providers or with any provider that supports SAML protocol:

  • Azure AD

  • Auth0

  • Okta

How can I have the Credentially SSO connected?

If you want to connect the Credentially SSO, please email support@credentially.io or contact your Customer Success Manager directly for a quote.

Note: Credentially will provide you with some specific service provider configuration information (Service Provider Entity ID, Callback URL, Metadata URL, etc) needed for the SSO setup. However, the SSO account setup itself will be required on your end.

What data is required to connect the Credentially SSO?

We need some data from you so we can connect you to SAML 2.0 integration:

  1. Provider Identity Entity Id (e.g. “http://www.okta.com/exkdfdggr334”);

  2. Active Provider Certificate (base64 encoded certificate, public)

    Certificate example:

    MIIDqDCCApCgAwIBAgIGAYKrsjeJMA0GCSqGSIb3DQEBCwUAMIGUMQswCQYDVQQGEwJVUzETMBEG A1UECAwKQ2FsaWZvcm5pYTEWMBQGA1UEBwwNU2FuIEZyYW5jaXNjbzENMAsGA1UECgwET2t0YTEU ... uIvkeKMRPfpM8QTjh/hzdZeY25zNZl+g1YI+KkGbvySi7f9P0GoTJ4aryxOVBmpzAvXBJ2eeCAR4 lVicgx/xTntPaAT8o0lEI+pZo9bCpTj2SWFJKQ== )

  3. Provider Service Entity Id (optional, but must be shared if a part of Provider configuration, e.g. “133hjh”)

  4. Provider Name (optional, e.g. “Okta“);

What our users will see once the SSO is connected?

Once the SSO functionality is connected to your organisation, the following SSO extension will be available for users on the sign up page:

Did this answer your question?