How spring-projects/spring-security-samples works
Project type and purpose
• This is a multi‐module “monorepo” of Spring Security sample applications. It groups dozens of small web apps and services illustrating different security scenarios (Servlet MVC, Spring Boot, WebFlux, RSocket, OAuth2, SAML2, JWT, LDAP, X.509, CAS, etc.). The README is purely a catalog of those samples.
File‐structure overview
• Top‐level “infrastructure”:
• .github/workflows – CI/CD definitions (GitHub Actions).
• config/checkstyle – quality rules applied across modules.
• docker/cas – Docker Compose to spin up a CAS server for CAS samples.
• build.gradle, settings.gradle, gradle.properties, gradle/… – root Gradle build orchestrating all subprojects, plus version catalogs and wrapper.
• scripts (sync‐*, find‐latest‐minor‐version.sh) – utility scripts for dependency/version management.
• Subproject groups:
• reactive/… – WebFlux, RSocket, WebFlux.fn, Kotlin WebFlux samples.
• servlet/… – Spring Boot (Java/Kotlin), pure Servlet Java‐Config, XML‐Config, AOT, OAuth2, SAML2, authentication variants, data integration, session management, observability.
• Each leaf directory under reactive/ or servlet/ is a standalone Gradle project with its own build files, source tree, and integration tests.
README insights
• The README maps each submodule to a use case (e.g. “OAuth2 login”, “Resource Server”, “JWT login”, “X.509”).
• No single system runs all modules at once—they’re independent samples. Some integration tests rely on external containers (CAS, LDAP, database scripts).
Diagramming this architecture
a. Main components:
• GitHub Monorepo (root)
• CI/CD (GitHub Actions workflows)
• Build System (Gradle root + multiproject)
• Quality Config (Checkstyle rules)
• Docker CAS environment
• Subproject groups (“reactive”, “servlet”)
• Individual sample apps (OAuth2 Authorization Server, WebFlux hello‐security, LDAP sample, etc.)
• External services (CAS server, LDAP directory, relational DB for JDBC samples)
b. Relationships & interactions:
• Commits → CI pipeline (trigger .github/workflows)
• CI → invokes ./gradlew build (loads settings.gradle → configures all subprojects)
• CI → spins up Docker CAS for CAS‐samples’ tests
• LDAP samples → LDAP directory (embedded or external)
• JDBC samples → relational DB (import.sql)
c. Architectural patterns & principles:
• Multi‐module Gradle build (composite/cross‐project)
• Containerization for external dependencies (Docker Compose)
• CI/CD enforcing consistency and code quality
• Each sample follows MVC / Reactive‐Streams / WebFlux.fn or pure Servlet configuration patterns
d. Key technologies:
• Spring Security, Spring Boot, Spring WebFlux, Spring MVC
• OAuth2 (Spring Security’s client, resource‐server, authorization‐server)
• SAML2 login/logout, JWT auth, X.509 client cert, multi‐factor, CAS
• RSocket (hello‐security sample)
• Gradle (settings.gradle, libs.versions.toml, wrapper)
• Docker Compose for CAS
• Checkstyle for styling