💡 SSO is an enterprise feature that requires a valid license purchased from Ninox or a certified partner.

SAML- and OIDC-based single sign-on (SSO) gives collaborators access to your Ninox Private Cloud through an identity provider (IdP) of your choice.

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's own login mechanism is deactivated. In this way, authentication security is shifted to your IdP and coordinated with your other service providers.

3 main configuration strategies for Private Cloud and On-Premises

• Security Assertion Markup Language (SAML)
  • Example setup 1: SAML SSO with Okta (rewrite in progress)
  • Example setup 2: SAML SSO with MS Entra
• OpenID Connect (OIDC)
  • Example setup: OIDC SSO with Okta
• Active Directory Domain Services (AD DS)
  • In progress

When using custom domains

To understand how a Private Cloud with custom domains needs to be configured to properly redirect to the domain of request origin, check out this article: SSO with custom domains.