Single Sign-on


Single Sign-on enables users to use a set of user account to access multiple application systems and the EnOS SSO service is used to address the authentication between the EnOS system and different business applications, allowing you to access all the added applications by logging in just once.

Supported Protocols

At present, the SSO supports client docking through OpenID Connect 1.0 and SAML 2.0 protocols.

Applicable Scenarios

Depending on different identity providers, the SSO service provided by EnOS is applicable for two types of scenarios.

  • EnOS as IdP: The enterprise-owned applications log in to other enterprise applications with EnOS accounts by docking with the EnOS SSO service.

  • Third-party authentication service proxy: The SSO service can be used as the proxy of third-party standard protocol-based authentication services, and can be connected as the client of the third-party authentication service.

Scenario 1: EnOS as IdP

EnOS SSO supports the configuration of two types of EnOS authentication services: EnOS Application Portal authentication and EnOS Management Console authentication. The enterprise applications can log in with EnOS accounts through simple development docking.

_images/sso_senario_2.png

Scenario 2: Third-party Authentication Service Proxy

The EnOS SSO service can be used as the proxy of third-party standard protocol-based authentication services, and can be connected as the client of third-party authentication service. The SSO service acts as a proxy for the third-party authentication service to the client so that a single client can dock with different authentication sources through the same protocol.


_images/sso_senario_1.png