mirror of
https://github.com/hanzoai/id.git
synced 2026-10-16 18:38:15 +00:00
zooqueen
aba085af6b
LoginForm no longer pins organization=<brand> on POST /v1/iam/login. It passes the new (normally-unset) TenantConfig.loginOrg, and client.login() OMITS the organization field when empty so IAM runs cross-org resolution and the session encodes the user's REAL owner-org (GetOrganizationByUser), never the hint. Fixes: global admins (z@/[email protected], [email protected] — owner=admin) were truncated to a 1-org 'hanzo' session via the UI because the pinned org made GetUserByFields hit the colliding hanzo/<name> row first, so the cross-org fallback to admin/<name> never ran. IAM IsGlobalAdmin()==(Owner=='admin') and get-organizations returns all orgs only for a global admin. Verified live on hanzo.id: [email protected] -> owner=admin, 45 orgs; brand-only user -> 1 org. Boundaries preserved: signup still sends a concrete org; per-app SSO (client_id+redirect_uri, type=code) still mints a code bound to the resolved user; a brand can force single-org login via loginOrg in the catalog ConfigMap. Contract locked in pkgs/auth/src/client.test.ts. Bump 0.1.22 -> 0.1.23.
@hanzo/id
White-label login + identity verification portal. One Vite SPA, four hosts
(hanzo.id, lux.id, zoo.id, pars.id), per-tenant brand resolved from
the request hostname at runtime.
Layout
apps/
web/ Vite + React 19 + @hanzo/gui — the actual SPA
k8s/ Deployment + Service + Ingress (4 hosts, 4 TLS secrets)
pkgs/
shared/ @hanzo/id-shared — TenantConfig + brand resolver
auth/ @hanzo/id-auth — composable login/signup/OTP flows
on top of @hanzo/iam SDK
idv/ @hanzo/id-idv — pluggable identity verification
(Persona, Onfido, Veriff, stub)
legacy-nextjs/ Frozen — predecessor Next.js implementation. Kept
for reference until v0.1.0 ships to production.
Local dev
pnpm install
pnpm dev # http://localhost:5173 (defaults to hanzo brand)
To preview a different brand locally, edit /etc/hosts:
127.0.0.1 lux.id zoo.id pars.id
then visit http://lux.id:5173.
Build
pnpm build # builds apps/web -> dist/
docker build -t ghcr.io/hanzoai/id:0.1.0 .
Adding a brand
- Publish or workspace-link the new per-org brand pkg (must ship
brand.jsonat the package root and match theBrandContractshape inpkgs/shared/src/types.ts). - Add a
DEFAULT_TENANTSentry inpkgs/shared/src/tenant.tsOR put the override in the runtime catalog (IAM_TENANT_CONFIG_JSONenv) so no rebuild is needed. - Add the hostname to
apps/web/vite.config.ts::BRAND_PACKAGES(lets dev + build serve/brand/<pkg>/brand.json). - Add the hostname + TLS secret to
apps/web/k8s/ingress.yaml. - DNS: CNAME or A record → cluster ingress IP.
That's it — no per-brand Worker, no per-brand image, no per-brand deployment. One binary, four brands.
Plugging an IDV provider
import { registerProvider, createPersonaProvider } from '@hanzo/id-idv'
registerProvider(createPersonaProvider({
templateId: import.meta.env.VITE_PERSONA_TEMPLATE_ID,
apiKey: import.meta.env.VITE_PERSONA_API_KEY,
environment: 'production',
}))
The portal stays unchanged — switching providers is a single registration call at boot.