Nia documentation · 4.0.0
Security, 2FA and OIDC
Configure passkeys, TOTP, recovery codes, trusted sessions and an OpenID Connect identity provider.Nia supports password authentication, TOTP, passkeys/WebAuthn, recovery codes and OIDC. Security-sensitive actions require fresh reauthentication when MFA is active.
HTTPS and public URL first
Before enabling passkeys or OIDC:
- Publish the instance through HTTPS.
- Save the exact public base URL in
/admin. - Confirm that the native app, browser and reverse proxy all use the same origin.
Passkeys are bound to this origin and relying-party ID. Non-localhost production passkeys fail closed without a configured public URL.
User 2FA
Users manage their factors in the app settings:
- authenticator-app TOTP
- passkeys
- single-use recovery codes
- active and trusted device sessions
Recovery codes are shown when generated and should be stored outside Nia. Removing the last primary factor also removes recovery-code access.
The administrator can require 2FA globally. Enable that policy only after confirming that users can enroll and that your account-recovery process is understood.
OIDC single sign-on
Nia supports a generic OpenID Connect provider using discovery. Register this redirect URI at the provider:
https://todo.example.com/api/oidc/callback
Then configure in /admin:
- provider display name
- HTTPS issuer URL
- client ID
- client secret, unless explicitly using a public client
- token authentication method (usually
auto) - scopes (default:
openid email profile)
OIDC users are matched strictly using a verified email address on both sides. The administrator’s OIDC identity must be linked manually from an authenticated admin session.
Module and shared-content access
The same authenticated account is used across Tasks, Shopping and Recipes. Hiding a module is a personal display preference, not an authorization boundary. Projects, shopping lists and cookbooks use ownership, household membership and accepted direct invitations to determine access. Participants may edit permitted content without having permission to manage the collection or its members.
Child records inherit the containing collection’s boundary. A Tasks attachment or recipe image is not public just because someone knows its URL. Upload quotas control new Tasks uploads; they do not replace permission checks for existing content. When access is revoked, connected clients reconcile and remove inaccessible cached content. A disconnected device cannot learn about a revocation until it reconnects.
BrainDump access is an additional global/per-user service permission; it does not grant access to another account’s content or personal destination memory. OIDC sign-in does not bypass collection ownership, household acceptance or these per-user service settings.
API keys
Users can create user-bound machine credentials from settings. API keys currently inherit the user’s API access rather than offering selectable permission scopes. They use the ApiKey nt_... authorization scheme and are intentionally separate from browser MFA challenges. Creating or revoking keys requires fresh MFA reauthentication when MFA is required.
Treat API keys like passwords: store them in a secret manager, do not embed them in public scripts and revoke unused keys.