LAS SSO

LAS SSO manages identity, credentials, account lifecycle, SSO sessions and first-party service-access eligibility. Business permissions and consumer databases belong to the relying applications.

Repository

Path	Purpose
las-sso-server/	Active Java 21 / Spring Boot / PostgreSQL application and the only active Gradle build
las-sso-server/las-sso-spring-boot-starter/	Reusable servlet BFF integration library
las-sso-server/las-sso-reference-bff/	Acceptance sample, not the LASLOG backend
docs/	Contracts, ADRs, historical evidence and paired English/Chinese records
scripts/	Portable repository/report verification tools
release/	Versioned delivery templates, independent handbooks and ignored generated packages
design/, research/	Reference assets and historical research
SAS-Test/	Ignored historical protocol demo; not an active module

Build And Verify

Requirements: JDK 21, Docker for PostgreSQL integration tests, Python 3.10+ for repository/report checks. Use the checked-in Gradle Wrapper; no global Gradle or workstation-specific init script is needed.

From the repository root:

python scripts/verify.py repository

From las-sso-server/:

.\gradlew.bat build -PrequireDatabaseTests=true --no-daemon --console=plain

From the repository root after the build:

python scripts/verify.py tests --require-no-skips

On Linux use ./gradlew for the same tasks. build includes Java formatting checks for all three modules. -PrequireDatabaseTests=true rejects skipped tests; Docker must be running. Focused local tests may omit that flag, but a skipped database suite is not persistence evidence.

Local Development

From las-sso-server/:

docker compose up -d
.\gradlew.bat bootRun --args="--spring.profiles.active=local"

SSO: http://127.0.0.1:9000. In a second terminal run :las-sso-reference-bff:bootRun, then visit http://127.0.0.1:8088. Keep one hostname throughout the flow. Local clients and ephemeral signing keys are development-only.

Documentation

• Server operation and maintenance
• Starter contract
• Reference BFF
• Versioned delivery packaging
• Implemented API reference / 中文 / OpenAPI3.1
• Contribution and engineering rules
• Engineering baseline / 中文
• Documentation index
• Current production launch plan / English

Historical delivery manifests identify their original source/artifact snapshots. Formatting and build-convention changes do not overwrite those deliveries or imply production readiness. New release inputs require a new identified combination.