Configure the policy
Password and passwordless flows
Use HttpOnly cookies for sensitive apps
The browser client’s compatibility default stores its opaque access and refresh pair inlocalStorage, which an XSS bug could read. Server-rendered and security-sensitive applications
should exchange callbacks and rotate refresh tokens only in server routes:
Domain attribute, serialize tokens into HTML, or send refresh tokens to browser
JavaScript. Apply CSRF protection to application writes. See the
App Auth SDK guide for the browser/server split.
Operations
Members can inspect configuration and users. Admins can update policy and revoke or disable application users. Owner session is required for provider credentials and destructive realm deletion. Audit events contain bounded metadata rather than passwords, links, or tokens. The App Auth TypeScript package is release-ready in the repository but is not yet available from the public npm registry. Do not add@korve-dev/app-auth as an npm dependency until anonymous
registry installation succeeds; use the REST contract or checked-out workspace source during
pre-release evaluation.
See the complete App Auth API.