Web Applications
A web application is an application that can be accessed through the web. The biggest advantage is that users can easily access the application with just a browser, without needing to install additional software. Applications have two modes: C/S and B/S. C/S is a client/server program, while B/S is a browser/server application that is accessed and authenticated through a web browser.
Web application development mainly consists of two parts. The first part is front-end program development, mainly implemented using HTML, JavaScript, and Vue, ultimately executed and displayed in the browser. The second part is server-side backend program development, mainly implemented using languages such as Java, .NET, PHP, Node.js, and Python.
Authentication Integration Protocols
The BambooCloud IDaaS identity cloud platform supports multiple authentication protocol integrations. Web applications can quickly and efficiently complete authentication integration with IDaaS. Developers can comprehensively consider factors such as the authentication protocols already supported by the application system and the difficulty of development to choose a suitable authentication protocol.
| Supported Protocol | Use Case | Recommendation |
|---|---|---|
| OAuth 2.0 Authentication | This is the most secure and commonly used web application integration. It uses the OAuth 2.0 standard authorization code mode, where the application obtains a temporary code after user authorization and exchanges it for a token. | ⭐⭐⭐⭐⭐ |
| OIDC Authentication | OIDC is a new-generation identity authentication standard protocol based on OAuth 2.0. OIDC provides user identity authentication information to third-party applications in the form of an ID Token. After the third-party application verifies the ID Token signature, it can parse and obtain the login user information. If the application developer is familiar with OIDC-related technologies, this protocol can be used. | ⭐⭐⭐⭐ |
| SAML Authentication | SAML is an XML-based federation authentication standard protocol. The SAML standard defines the Identity Provider (IdP) and Service Provider (SP), solving identity authentication and single sign-on problems between different cross-domain application systems. It is mainly used for web applications, but the rules defined by the protocol are relatively complex, bringing significant development challenges to application developers. Therefore, internally developed enterprise systems rarely use this protocol for integration; it is more commonly used in mainstream commercial large-scale application systems. | ⭐⭐ |
| CAS Authentication | CAS is a B/S architecture single sign-on (SSO) protocol, but the scenarios it addresses are relatively simple. There are not many applications on the market that implement the CAS protocol, so we do not recommend this protocol. | ⭐ |
| WS-Fed Authentication | This standard is based on SOAP. Although the entire protocol is powerful and considers details comprehensively, its implementation is relatively heavy. It is only prioritized when integration with Microsoft services is required. | ⭐ |