Standard protocols supported by IDaaS

Enterprise identity management systems use internationally recognized and widely adopted identity management protocols. Mature enterprise software often follows international standard protocols so that its customers can integrate the software with their own IdP. In this context, the IdP is IDaaS.

Procedure

IDaaS allows any application that supports standard protocols to integrate with single sign-on through configuration.

Go to Applications and click Add Application.
On the Standard Protocols tab, select a SAML 2.0 application or an OIDC application based on your requirements, and then click Add Application to start configuring the standard protocol application.

Advantages of using standard protocols

For applications, supporting standard protocols provides the following benefits:

Greater maturity. Supporting standard identity protocols is an important indicator of a mature enterprise application.
Greater universality. Standard protocols do not lock you into an enterprise account system. Integrating with one standard protocol lets customers choose the identity provider that suits them best.
Greater security. Self-developed protocols almost certainly have security flaws. International standard protocols go through a rigorous publication process, cover a complete set of use cases, and provide security assurance.

Note

Integrating with a standard protocol takes only a short time. If you are an enterprise application vendor and want to integrate with a standard protocol, contact us for help. We will also list your enterprise application in the IDaaS application marketplace so that it gains targeted public exposure.

Standard protocol	Description
OIDC	Published in 2014, the OpenID Connect (OIDC) protocol provides the best configuration and integration experience and performance in modern identity systems. It adds a JWT-based `id_token` on top of the OAuth 2.0 authorization protocol and supports both authentication and authorization use cases.
SAML 2.0	Published in 2005, SAML 2.0 remains the most common single sign-on protocol in the world. The vast majority of mature enterprise applications support SAML integration. For historical reasons, SAML 2.0 is built on XML, which makes it less adaptable in some edge cases.
OAuth 2.0	Published in 2012, OAuth 2.0 (RFC 6749) is the most general-purpose authorization delegation protocol. The protocol distinguishes the authorization server (AS) from the resource server (RS), and is lightweight and flexible. Common examples, such as logging on with WeChat and scanning a QR code to log on with DingTalk, use the OAuth 2.0 protocol. OIDC encompasses the capabilities of OAuth. In IDaaS, you can use OIDC instead of OAuth.
CAS `future` `version`	Central Authentication Service (CAS) 3.0 was published in 2013. CAS was created and is maintained by Yale University, and is supported by many applications.

In a search engine or the application documentation, search for the application name followed by single sign-on, or for application_name followed by SSO, to check whether the application you want to integrate supports a standard single sign-on protocol. If the application supports standard protocols, you can submit a request to us. We will list the application in the application marketplace shortly so that you and subsequent customers can use it.