Identity, authorization, secret ownership and sensitive-data requirements for Encik Beku.
Authentication is provided by the shared UtopiaSpace Supabase project. A JWT subject corresponds to the shared Hub identity. Possessing a valid shared token is not sufficient for application access: Encik Beku provisions and authorizes a separate local app_users record.
The application supports direct Google OAuth and shared-domain silent SSO. Silent SSO adopts only the access token and deliberately does not rotate or copy the shared refresh token.
Authorization combines:
Backend middleware is authoritative. Frontend navigation and button visibility are convenience controls only.
High-risk permission areas include user/role administration, company configuration, finance verification, integrations/API tokens, order mutation, item master/account data and cross-branch access.
API tokens are administered through protected routes and carry explicit scopes such as ops, oe, reports or finance. During handover:
The cross-cutting rules require:
| Class | Examples | Expected owner |
|---|---|---|
| Application | APP_KEY, cookie policy |
Backend/platform owner |
| Database | PostgreSQL URL or host/user/password | Database/platform owner |
| Identity | Supabase URL/keys and JWT verification configuration | Hub identity owner plus application owner |
| Storage | S3-compatible access keys and buckets | Platform/storage owner |
| Integrations | OE partner and vehicle-listing secrets | Owning integration teams |
| Deployment | Vercel, DigitalOcean and GitHub credentials | Release/platform owner |
| Documentation automation | Wiki repository token and model provider key | Repository administrators |
Secret values belong in the approved secret manager and hosting dashboards, not Markdown, source control, chat or incident tickets.
The source documents design intentions but does not by itself prove:
These require live-environment evidence during handover.