Old North Observatory
Science & discovery · Sample record
IDENTITY & ACCESS / INTERACTIVE SPECIFICATION
Explore how a self-hosted identity provider and a backend session
keep responsibilities clear.
In the real application, sign-in happens at Keycloak — not in a password form built here.
No password, identity-provider credentials or personal data is requested.
UNDERSTAND THE BOUNDARIES
Changing this selector is a local teaching tool.
Real role assignment belongs to Keycloak admins.
The actual directory and API have no anonymous mode.
Science & discovery · Sample record
Fortification · Sample record
Engineering · Sample record
LEAST PRIVILEGE, EXPLICIT GRANTS
| Capability | Viewer | Editor | Admin |
|---|---|---|---|
| List & read locations | ✓ | ✓ | ✓ |
| Create, update & delete locations | — | ✓ | ✓ |
| Manage accounts & role grants | — | — | Keycloak console |
Accounts, password changes, role assignments, temporary-password resets and disable/delete actions stay in the provider. No application user-administration endpoints are defined.
OIDC authorization code + PKCE. Tokens stay in a server-side in-memory session; the browser receives an HttpOnly, Secure, SameSite=Lax cookie. Thirty minutes idle expiry; restart logs everyone out.
Only login entry/callback endpoints are public in the application policy. A read-only public map and bearer-token MCP access are distinct post-MVP components.
The general policy says every authenticated user is implicitly a viewer. The later social-login section says a new provider user without roles cannot act until a grant. These statements require reconciliation. This demo shows the stricter pending-role social case separately and does not claim that ambiguity is resolved.
FOLLOW A SESSION
Google is brokered through Keycloak in the source stage environment. An existing email match is denied until the user signs in and explicitly links the provider. Apple is not selected.
The ingress routes the avarc realm and resources under /auth. Admin, master realm and management port 9000 stay off public ingress. JSON logs exclude login-code query strings; events are held for 30 days.
Database backup is primary. User exports preserve IDs, provider links and explicit roles; local passwords need reset after API-only restore. No backup or personal record is accessed in this demo.