Single sign-on (SSO)

SAML- and OIDC-based single sign-on (SSO) gives collaborators access to your Ninox Private Cloud through an identity provider (IdP) of your choice (e.g., Okta).
By using SSO, collaborators will be able to log into Ninox using the familiar identity provider interface, instead of the Ninox login page. The collaborator's browser will then forward them to Ninox. The IdP grants access to Ninox when SSO is enabled and Ninox' own login mechanism is deactivated. In this way, authentication security is shifted to your IdP and coordinated with your other service providers.‌​
Ninox offers three different configuration strategies for Private Cloud:
1.​SAML 2.0 (Security Assertion Markup Language)​
2.​OIDC (OpenID Connect)​
3.AD DS (Active Directory Domain Services) (not yet covered in manual)
SSO is an enterprise feature that requires a valid license purchased from Ninox or a certified partner​
If you ordered custom-built features like SSO, you are eligible to receive an updated license. Whether you're using Ninox via Private Cloud or On-Premises, reach out to our Product team at [email protected] when you're ready to update.
Private Cloud: you request the update, we deploy it
On-Premises: you request the update, we send you a link, and you deploy it yourself
Additional resources
What Is Single Sign-On (SSO)?
What is SAML and how does SAML Authentication Work
Auth0 - Blog
What is OpenID Connect and what do you use it for? - Auth0
auth0
What is single sign-on? - Azure AD
docsmsft
Azure Single Sign On SAML Protocol - Microsoft identity platform
docsmsft
​
​

API - Previous

Private Cloud APIs

SAML single sign-on with Okta

Last modified 5mo ago

Export as PDF

Copy link

Contents

Additional resources