This article compares SSO and OAuth 2.0, detailing the CAS-based SSO authentication flow, OAuth 2.0's four grant types (authorization code, implicit, password, client credentials), and clarifies how OAuth 2.0 can implement SSO while distinguishing both from security frameworks like Spring Security and Shiro.
Authorization Code GrantCASClient Credentials Grant
This comprehensive guide analyzes authentication and authorization framework selection across five dimensions, comparing Sa-Token, Keycloak, Spring Security, and JWT with cost models, migration strategies, source code insights, and scenario-based recommendations for startups to enterprises.
This chapter from "Architecture Fundamentals: From Requirements to Architecture" dissects login system design, separating authentication, session management, and authorization, covering multi-factor methods, SSO, OAuth 2.0, QR-code login, multi-device sessions, and a practical design checklist with common pitfalls.
This article provides a comprehensive technical analysis of Sa-Token 1.39.0, covering source code architecture, scenario-based configurations for JWT/stateless auth, mobile multi-device, RBAC admin panels, and SaaS multi-tenancy, plus unit testing patterns, common misconceptions, performance comparisons with Spring Security and Shiro, and production hardening practices.
This article explores MaxKey, an open-source single sign-on system supporting OAuth 2.x, OpenID Connect, SAML 2.0, JWT, CAS, and SCIM, detailing its microservices architecture, security features like secondary authentication and single logout, session timeout design, brute-force protections, and bcrypt password storage implementation.
Hacktron AI researchers used Claude to discover a libheif memory corruption bug in OpenAI's Discourse forum, achieve remote code execution, hijack employee SSO sessions, access Codex-linked internal GitHub, and submit a pull request to openai/openai — all within 72 hours at under $3,000 model cost.
This article explains how to implement Single Sign-On (SSO) using CAS to unify authentication across multiple company systems, covering session mechanics, cluster session sharing with Redis, and providing complete Spring Boot code examples for both the CAS server and client applications.
The article analyzes the security debt caused by fragmented authentication across backend, portal, mobile and AI‑Agent services, introduces Casdoor – an open‑source, self‑hosted IAM/SSO platform that unifies identity, supports multiple protocols, AI‑native MCP/A2A auth, and provides detailed deployment, integration and comparison guidance.
This article provides a practical guide to integrating Spring Boot with Keycloak for unified authentication and single sign-on using OIDC authorization code flow, covering Keycloak deployment, realm and client configuration, Spring Security setup with role mapping for both browser login and resource server tokens, method-level authorization with @PreAuthorize, and extensions for multi-tenancy, LDAP federation, and Admin API.
This comprehensive guide compares Session-Cookie, JWT, OAuth2.0, and SSO authentication schemes, details production-ready dual-token JWT implementation with RS256, Redis blacklist/whitelist, Spring Cloud Gateway filters, and covers concurrency, revocation, and security hardening with code examples and interview insights.
The article explains why traditional session mechanisms break in clustered and multi‑service environments, compares session replication and centralized storage, introduces CAS‑based single sign‑on with ticket flow, contrasts it with OAuth2, and provides a complete Spring‑Boot demo with Redis‑backed session handling.
This article presents a detailed technical blueprint for building an enterprise‑grade single sign‑on system that combines Apereo CAS, OAuth2, and JWT across four microservices, covering service responsibilities, data models, API contracts, deployment trade‑offs, and operational safeguards.
This article systematically explains the concepts, workflows, advantages, drawbacks, and practical code examples of Cookie, Session, Token, OAuth2.0, Single Sign‑On (SSO) and JWT, compares them, offers best‑practice recommendations, and provides interview‑style Q&A for developers.
When a company’s internal tools each required separate logins, the team built an enterprise‑grade CAS single sign‑on system that unified identity, login entry, logout handling, and extensible integration, and they document the entire process across nine detailed articles.
This article examines the challenges of managing user authentication across many corporate systems, explains traditional session mechanisms, explores session sharing solutions for clustered environments, and provides a detailed walkthrough of implementing single sign‑on using CAS with Java and Redis, including code samples and a comparison with OAuth2.
This article systematically explains ten common authentication approaches—from basic HTTP authentication and session‑cookie mechanisms to token, JWT, SSO, OAuth 2.0, QR‑code login, and one‑click login—detailing their principles, workflows, advantages, drawbacks, and typical usage scenarios with concrete examples and code snippets.
When dozens of services rely on a shared SSO, a simple ping or HTTP 200 does not guarantee users can log in; this article compares common monitoring approaches, explains why a simulated‑login probe using Playwright is chosen, and details the design, implementation, and Linux deployment of the sys‑monitor tool that automatically validates the full login chain and alerts on failures.
This article explains Single Sign-On (SSO) fundamentals, detailing its three core components—CAS Server, CAS Client, and Browser—illustrating the overall architecture and walking through the complete authentication flow from accessing a service to ticket validation.
This article explains OAuth 2.0 by contrasting it with SSO, walks through a real‑world analogy, details the nine‑step authorization flow, defines key terms and roles, and describes how web servers, user agents, and native apps participate in the protocol.
The article examines the challenges of multiple corporate systems requiring separate logins, explains traditional session mechanisms and their limitations in clustered environments, compares session replication versus centralized storage, and presents a complete Java Spring implementation of CAS‑based single sign‑on with code samples and a discussion of differences from OAuth2.
This tutorial guides you through deploying Keycloak identity provider using Docker Compose on CentOS 7.9, covering environment setup, docker-compose.yml configuration with start-dev mode, admin initialization, port mapping, service verification, and common troubleshooting tips for development and testing environments.
This comprehensive guide explains why authentication is the traffic, permission, and trust entry point in modern high‑concurrency systems, compares Cookie, Session, JWT, OAuth2.1 and SSO, and provides detailed architectural patterns, trade‑offs, implementation steps, and production‑grade best practices for building secure, scalable identity solutions.
This article explains the core concepts of Single Sign‑On (SSO), detailing the roles of the CAS Server, CAS Client, and browser, and walks through the complete authentication flow with diagrams, illustrating how a single login grants access to multiple systems.
This article explains three core Single Sign-On architectures—same‑domain cookie/session, distributed token‑based (JWT/OAuth2), and Central Authentication Service—detailing their workflows, advantages, drawbacks, and ideal use cases, helping architects choose the right SSO solution for web, mobile, and micro‑service environments.
This article explains the principles of Single Sign-On (SSO) and OAuth2.0, compares their workflows, outlines the four OAuth2.0 grant types, and clarifies terminology differences, providing clear step‑by‑step diagrams and practical examples.
This article systematically introduces ten widely used authentication methods—including HTTP Basic Auth, Session‑Cookie, Token, JWT, Single Sign‑On, OAuth 2.0, federated login, unique‑device login, QR‑code login, and one‑click mobile login—explaining their principles, workflows, advantages, drawbacks, and typical implementation libraries.
Single Sign-On (SSO) lets users authenticate once and automatically gain access to all trusted applications, eliminating repeated logins and streamlining user experience across heterogeneous systems such as e‑commerce, payment, and collaboration platforms.
This article walks through a complete design and implementation of a unified single sign‑on system using OAuth2.0 authorization‑code flow, Spring Cloud Gateway, JWT, Redis, and Nacos, comparing JWT, authentication, and authorization while presenting performance metrics, security considerations, and interview‑ready answers.
This article explains the fundamentals of Single Sign-On (SSO), detailing its centralized authentication principle, the roles of CAS Server, CAS Client, and browser, and walks through the complete login flow with diagrams and code snippets for distributed systems.
This article explains the fundamentals of Single Sign-On (SSO), describing its purpose of simplifying user authentication across multiple services, the core components such as CAS Server, CAS Client, and the browser, and walks through the step‑by‑step authentication flow with illustrative diagrams.
SSO (Single Sign‑On) and OAuth2.0 are both widely used identity frameworks; SSO handles user authentication across multiple applications with a single login, while OAuth2.0 is an authorization protocol that lets users grant third‑party apps limited access to resources without sharing passwords.
This guide explains the core concepts, architecture components, authentication flow, and real‑world deployment scenarios of Single Sign‑On (SSO) systems, helping architects build unified, secure login solutions for web, mobile, and micro‑service environments.
This article explains the concepts of Single Sign‑On (SSO) and the Central Authentication Service (CAS), then provides a detailed, code‑rich tutorial for setting up a CAS server, configuring clients, disabling HTTPS for development, and testing the end‑to‑end SSO workflow using Java and Spring.
This guide walks you through configuring Keycloak as an OAuth2/OIDC identity provider for Nightingale monitoring, covering prerequisites, client and user creation in Keycloak, Nightingale OIDC settings, and verification steps to achieve seamless single sign‑on in enterprise environments.
Warpgate is an open‑source, Rust‑crafted bastion host that delivers secure, transparent, and high‑performance remote access for SSH, HTTPS, MySQL, and PostgreSQL without requiring any client software, offering native 2FA, SSO, session auditing, and a single 30 MB binary deployment.
Single Sign-On (SSO) is an authentication mechanism that lets users log in once to access multiple trusted applications, and this article breaks down its core components—Identity Provider, Service Providers, and business systems—along with a step‑by‑step flow illustrated with diagrams.
This article compares Single Sign‑On (SSO) and OAuth2.0, detailing their conceptual distinctions, token‑based workflows, implementation frameworks like CAS, the four OAuth2.0 grant types, and how each can be used to achieve seamless authentication across applications.
This comprehensive tutorial explains front‑end Single Sign‑On (SSO) concepts, covering cookie‑based, token‑based (JWT), and OAuth 2.0 implementations with detailed React code, session checking, token refresh, API interception, cross‑origin solutions, and security best practices.
This article explains why multiple independent login systems hurt user experience and security, reviews traditional session mechanisms and their limitations in clustered environments, and then presents two session‑sharing strategies and a complete CAS‑based SSO solution with Java code examples.
This article explains the fundamentals of Single Sign-On (SSO), detailing its cross‑system authentication mechanism, core components such as CAS Server, CAS Client, and User Agent, and walks through the step‑by‑step flow that enables users to log in once and access multiple trusted applications seamlessly.
This article explains the concept of Single Sign-On, its advantages, and two practical implementations using ticket‑based authentication and encrypted user data exchange between Service A and Service B, complete with database schema, configuration files, and full Java code examples.
This article provides a comprehensive overview of OAuth2.0, explaining its core concepts, the roles of resource owner, client, authorization server, and resource server, illustrating the full authorization flow with diagrams, clarifying related terminology such as authentication, delegation, and roles, and finally noting additional promotional material.
This article explains the limitations of traditional HTTP session handling, explores session sharing strategies for clustered environments, and demonstrates how to build a single sign‑on solution using CAS and OAuth2 concepts with complete Java code examples for filters, controllers, and login pages.
This article explains the pain points of multiple logins in enterprises, introduces Single Sign‑On concepts and protocols, outlines its benefits, and provides a step‑by‑step guide to deploy an open‑source Golang‑Vue SSO solution using Docker Compose.
This article provides a comprehensive overview of Single Sign-On (SSO), explaining its core concepts, authentication flow, token generation and validation, and practical use cases across enterprises, education, finance, and e‑commerce, while also offering insights into security benefits and implementation details.
This article explains the fundamentals, architecture, workflow, and practical scenarios of Single Sign-On (SSO), illustrating how a centralized authentication server enables users to log in once and seamlessly access multiple trusted applications, while also offering resources for deeper study.
This article explains the concepts, differences, and implementation steps of third‑party login and SSO, introduces the open‑source JustAuth library, and provides practical guidance and examples for integrating OAuth‑based authentication into web or mobile applications.
This guide explains the challenges of multiple logins in enterprises, introduces Single Sign‑On concepts and protocols, and provides a step‑by‑step deployment of an open‑source Go‑Vue SSO solution, covering authentication methods, supported protocols, security features, and Docker‑based installation.
The article examines a single sign‑on loop‑login problem caused by Secure‑flagged cookies being set over HTTP, explains how missing tokens trigger endless redirects, and recommends enforcing HTTPS or using a non‑Secure auxiliary token to break the redirect cycle.
This article explains traditional session mechanisms, challenges in clustered environments, and presents solutions such as session replication and centralized storage, then details the design and implementation of a CAS-based Single Sign-On system in Java, including code for user forms, controllers, filters, and configuration.
This article explains the concept of Single Sign‑On (SSO), outlines its implementation process—including user redirection, token generation, and cross‑system authentication—discusses challenges such as single point of failure, complexity, and cross‑domain issues, and highlights typical use cases in enterprise and e‑commerce environments.
This article explains the challenges of multiple product logins, reviews traditional session mechanisms, discusses session sharing solutions in clustered environments, and presents a CAS‑based single sign‑on implementation with Java code examples, highlighting differences between CAS and OAuth2 for secure authentication.
This article explains the OAuth2.0 authorization protocol, distinguishes it from single sign‑on, describes its core entities and step‑by‑step flow, and outlines how web servers, user agents, and native applications interact to securely obtain access tokens for protected resources.
This article explains the concept, definitions, and three deployment types of Single Sign-On (SSO), introduces the Central Authentication Service (CAS) mechanism, and details step‑by‑step login and logout processes across multiple web applications, illustrating each flow with diagrams and examples.
This article provides a comprehensive walkthrough of Single Sign‑On (SSO) concepts, common protocols, login flow diagrams, and multiple implementation options, then dives into step‑by‑step deployment of an enterprise‑grade SSO system using Keycloak with Docker or Kubernetes, including configuration, client setup, custom extensions, and practical code snippets.
This article traces the evolution of login authentication across system architectures—from monolithic apps using cookies and sessions, through front‑end/back‑end separation and CORS, to distributed systems employing SSO and stateless JWT, highlighting their mechanisms, challenges, and trade‑offs.
This guide walks through integrating OAuth2 Single Sign-On into a Laravel application using Laravel Passport, covering prerequisites, installation steps, configuration of the authentication server and client, testing procedures, and common troubleshooting tips to enhance security and user experience.
This article explains how Single Sign-On (SSO) and OAuth2.0 enable seamless authentication across micro‑service applications, compares session‑based, token‑based, OAuth‑based, and SAML‑based SSO approaches, outlines OAuth2.0 grant types, and introduces popular frameworks such as Spring Security OAuth, Keycloak, and Apache Oltu.
This article explains the principles of Single Sign‑On (SSO) and OAuth2.0, compares their workflows, describes the main steps of each protocol, outlines the four OAuth2.0 grant types, and clarifies the distinctions between SSO, OAuth2.0, JWT, and Java security frameworks.
This article explains the Central Authentication Service (CAS) single sign‑on system, detailing its token‑based architecture, the roles of the CAS server, client, and protected services, and outlines typical scenarios such as e‑commerce, enterprise intranets, online platforms, and cloud services.
This article explains the fundamentals of Single Sign-On (SSO), why it is needed in distributed systems, details the components and workflow of the CAS (Central Authentication Service) implementation, and outlines common application scenarios such as e‑commerce, enterprise portals, education, and finance.
This article walks through the fundamentals of HTTP session handling, the challenges of session sharing in clustered environments, and presents a step‑by‑step design of a Single Sign‑On solution using CAS, including concrete code examples, Redis‑based session storage, and a comparison with OAuth2.
This article explains the problems of traditional session management in multi‑service environments, introduces session replication and centralized storage (using Redis), and demonstrates a complete CAS‑based single sign‑on solution with Java code examples for user, controller, filter, and configuration components.
This article explains the concept, advantages, and implementation methods of Single Sign‑On (SSO) and provides two complete hands‑on examples—including architecture diagrams, database schema, configuration, and Java code for token‑based, ticket‑based, and RSA/AES encrypted SSO flows—using SpringBoot, Vue and Uni‑App.
This article explains the concept, advantages, and three implementation methods of Single Sign-On (SSO), then provides two complete practical examples—including architecture diagrams, step‑by‑step flows, and full Java code for ticket‑based and encrypted data‑based SSO—followed by supplementary RSA key generation notes and a brief promotional note.
This article explains the fundamentals of Single Sign‑On (SSO) and OAuth2.0, compares their token‑based authentication mechanisms, details typical implementation flows such as CAS, and clarifies the distinctions among SSO, OAuth2, JWT, Spring Security and Shiro, while also noting related promotional content.
This article reviews the shortcomings of simple cookie‑based single sign‑on, introduces a unified authentication center architecture, explains the Central Authentication Service (CAS) design and its deployment, and walks through the complete login process—including first, second, and cross‑domain accesses—highlighting key tickets, filters, and session handling.
This article explains the concepts, architecture, core tickets, and practical implementation steps of CAS-based Single Sign-On, including detailed API specifications, security considerations, and example code snippets for integrating SSO across multiple applications.
This tutorial explains how to build a PHP-based single sign‑on system using a main login application, a shared authentication service backed by MySQL and Redis, and multiple external applications, providing complete code examples for database setup, login handling, session sharing, and logout.
This article explains the principles of Single Sign‑On (SSO) and OAuth2.0, compares their workflows, describes the four OAuth2.0 grant types, and clarifies the distinctions between SSO, OAuth2.0, and Java security frameworks such as Spring Security and Shiro.
This article explains the concepts, workflows, and key differences between Single Sign‑On (SSO) and OAuth2.0, illustrating how token‑based authentication replaces passwords, detailing typical CAS‑based SSO steps, OAuth2.0 authorization‑code flow, and clarifying related terminology and grant types.
This article explains the principles and workflow of Single Sign‑On (SSO) and OAuth 2.0, compares their concepts, details implementation steps and grant types, and concludes with a promotional invitation to join a community offering related resources and discounts.
This article explains the fundamental concepts, roles, and step‑by‑step flow of OAuth 2.0, compares it with single sign‑on, describes the architecture of authorization, resource, and client servers, and clarifies related terminology such as authentication, federation, and delegated access.
This article explains the concept, background, and definition of Single Sign‑On (SSO), outlines three SSO deployment types, introduces the Central Authentication Service (CAS) with detailed ticket mechanisms, and provides step‑by‑step SSO and Single Logout (SLO) processes for multiple applications.
MaxKey is an open-source, Apache-licensed SSO platform that supports major authentication protocols, offers extensive login methods, provides multi-tenant IAM features, and includes detailed Linux deployment steps with code snippets and interface screenshots, making it a comprehensive solution for enterprise identity management.
This article analyzes the limitations of traditional HTTP session mechanisms in single‑server and clustered environments, explains why session sharing is essential for multi‑system products, and presents practical solutions such as session replication and centralized Redis storage, followed by a detailed walkthrough of CAS‑based single sign‑on implementation with Java Spring code examples and a comparison to OAuth2.
This tutorial walks through building a single sign‑on (SSO) solution using OAuth2, Spring Security, and JWT in a Java Spring Boot backend, covering preparation, Maven dependencies, server and client configurations, custom login pages, token handling, logout strategies, project structure, and a full demo with source code.
This article provides a step‑by‑step guide on building a Single Sign‑On solution using OAuth2, JWT tokens, and Spring Security within a Spring Boot application, covering the underlying concepts, Maven dependencies, configuration files, server setup, client integration, and logout handling.
This article explains the concepts and differences between Single Sign-On (SSO) and OAuth2.0, describing their token-based authentication flows, typical implementations such as CAS, the four OAuth2.0 grant types, and how they can be used to achieve seamless login across applications.
This article provides an in‑depth overview of authentication, authorization, and permission control concepts and compares ten common front‑end authentication techniques—including HTTP Basic Auth, Session‑Cookie, Token, JWT, SSO, OAuth 2.0, QR‑code login and one‑click login—detailing their workflows, advantages, drawbacks, and typical usage scenarios.
This article explains the principles of Single Sign‑On (SSO) and OAuth2.0, compares their workflows, describes common implementation patterns such as CAS and token‑based authentication, and clarifies the distinctions between SSO, OAuth2.0, and related security frameworks.
This article explains the principles of Single Sign-On (SSO) and OAuth2.0, compares their concepts, outlines typical SSO workflows using CAS, details OAuth2.0 authorization code flow, clarifies terminology differences, and discusses related security frameworks such as Spring Security and Shiro.
This article provides a comprehensive tutorial on implementing Single Sign-On using the Central Authentication Service (CAS), covering its concepts, features, architecture, environment setup, server and client configuration, and testing procedures with detailed code examples for Java developers.
This article explains the concepts, relationships, and practical implementations of authentication, authorization, and access control, and compares ten common frontend authentication methods—including HTTP Basic, Session‑Cookie, Token, JWT, SSO, OAuth, and QR‑code login—detailing their workflows, advantages, disadvantages, and suitable scenarios.
This article explains the principles and workflow of Single Sign‑On using OAuth2.0, illustrates the process with a real‑life analogy, and provides a complete Spring Boot example—including authorization server, client configuration, and role‑based access control—suitable for microservice architectures.
This article explains the challenges of multiple product systems, reviews traditional session mechanisms and their limitations in clustered environments, compares session replication and centralized storage using Redis, and details the design and implementation of Single Sign-On using CAS and OAuth2 with Java Spring code examples.
This article explains the concept of Single Sign‑On (SSO), compares its major protocols—SAML, OAuth2, and OpenID Connect—covers their workflows, benefits, terminology, and provides guidance on when to choose each protocol for different application scenarios.
This article explains the fundamentals of Single Sign‑On (SSO), compares the two most common protocols—SAML and OAuth2 (with OpenID Connect)—covers their terminology, workflows, benefits, and provides guidance on which to use in different scenarios.
This article explains single sign‑on concepts, compares SAML, OAuth2 and OpenID Connect, outlines their benefits and typical workflows, and provides guidance on choosing the right protocol for different security and user‑experience scenarios.
This article analyzes why an iOS SSO QR‑code login sometimes fails with a 404 error despite being on company Wi‑Fi, explains the 301 redirect caused by network restrictions, and provides a step‑by‑step solution using NSURLCache inspection and cache‑clearing techniques.
This article explains the limitations of traditional HTTP session handling, explores session sharing strategies for clustered environments, and walks through a complete Java CAS‑based single sign‑on solution with code examples, highlighting the differences between CAS and OAuth2.
This article explains the challenges of traditional session mechanisms in distributed systems, explores session sharing solutions such as replication and centralized storage, details the design and flow of Single Sign‑On (SSO) using CAS, compares CAS with OAuth2, and provides complete Java code examples for a demo implementation.
This article provides an in‑depth guide to authentication, authorization, and access control, covering basic HTTP authentication, session‑cookie mechanisms, token‑based approaches, JWT structure, single sign‑on (SSO), OAuth 2.0 flows, unique login enforcement, QR‑code login, and one‑click mobile login, with practical code examples and diagrams.
The article explains the concepts of Single Sign-On and OAuth2.0, compares their trust, resource, and flow differences, and details how to implement SSO using OAuth2.0 or the CAS framework, while also promoting related Spring Cloud Alibaba video tutorials.
This article explains traditional session and authentication mechanisms, the problems of session sharing in clustered and multi‑service environments, and presents practical SSO solutions—including CAS‑based single sign‑on and its differences from OAuth2—accompanied by complete Java Spring code examples.
This article explains the limitations of traditional HTTP session mechanisms, explores session sharing strategies in clustered environments, and provides a detailed walkthrough of implementing Single Sign-On using CAS, including code samples and a comparison with OAuth2 authentication.
This article explains why unified authentication is essential for product suites, reviews traditional session mechanisms and their limitations in clustered environments, explores session‑sharing strategies, introduces CAS‑based SSO workflows, compares CAS with OAuth2, and provides a complete Spring Boot demo with code snippets and configuration details.