This page is about readers using SSO to sign in to your private docs. If you're looking for editors using SSO to sign in to DeveloperHub, see Editor Single Sign-On (SSO).
With SSO, you can manage reader access to a DeveloperHub docs site using an identity provider.
DeveloperHub supports SAML 2.0, which works with but not limited to:
- Okta
- OneLogin
- Azure
- Active Directory (ADFS)
Process for Setting Up SSO
The process for setting up SSO is as follows:
Contact us to let us know that you require SSO, providing us with which IdP you are integrating with.
We will provide you with an
sso_idwhich you can use to get the ACS URL. The ACS URL and Entity ID are as follows:- ACS URL:
https://auth.developerhub.io/login/callback/<sso_id> - Entity ID:
https://auth.developerhub.io/reader
- ACS URL:
We will then require from you
- IdP SSO URL.
- IdP Issuer.
- Are responses signed?
- X.509 certificate.
Logging in Readers
To login readers, they can:
- Initiate a session from your IdP.
- Login directly through the docs site.