Architecture
Native / browser client ── Authorization Code + PKCE ── Keycloak (idp.gorapeflutter.site)
│ │
│ access token │ iss + sub / AMR
└───────────────────────────► Gorape API (api.gorapeflutter.site / RP ID: gorapeflutter.site) ◄──┘
│ │
PostgreSQL Redis
The server normalizes listener host/port, TLS, OIDC, attestation, and WebAuthn settings from configuration (GF-10037 and starts the HTTP listener and an optional TLS listener (GF-10001; the router composes auth, rate-limit, CORS, and request-ID middleware with the REST controllers (GF-10002.
Gorape is not an identity provider. Keycloak owns users, passwords, and login
sessions. Gorape validates access tokens and resolves principals by iss + sub
(GF-10003, GF-10005, GF-10006). The platform-provisioning API uses a
separate configured issuer and role gate (GF-10004, GF-10023, GF-10024).
Gorape stores only project-scoped principals, groups, roles, devices, public
keys/WebAuthn credential state, verified attestation summaries, and audit
events. Gorape passkeys are a separate RP credential from Keycloak passkeys.
Project-scoped tables and repository queries are isolated by project_id.
Effective permissions combine Gorape role bindings and dynamic Keycloak claims
(GF-10007, GF-10025). Device registration and possession operations also
require a validated amr: ["passkey"] claim (GF-10008); challenges are
short-lived, project/subject/purpose-bound, and consumed once (GF-10009). Root
Domain is a cluster boundary and is not managed by the database or REST API.