Skip to content

The v1 docs follow nauthera-server's main branch and its 0.x releases on the way to 1.0, so fields and APIs can still change.

v1

registration_disabled

Docs version v1 (main)Nauthera is pre-1.0, in a design-partner program

Self-service registration is turned off on this deployment (403).

Meaning

POST /v1/auth/register was called while auth.registration.enabled is false, which is the default. Accounts are then created by administrators, by invitation or through an identity provider.

Impact

A visitor cannot create an account. It is expected on a deployment that does not offer sign-up; if sign-up should be offered, it is a configuration gap.

Diagnosis

The refusal is recorded as auth.registration.completed with reason registration_closed. Check auth.registration.enabled in the loaded configuration.

Mitigation

  • As a user: ask the organization's administrator for an invitation.
  • As an operator: set auth.registration.enabled: true only if sign-up is wanted. A duplicate address then answers registration_conflict, which tells the caller the address is taken, so front it with the captcha and rate limits.

Escalation

Escalate when registration is enabled in the configuration and still refused. Open an issue with the request id, the configuration source and the server version.

Problem code runbooks · Generated from internal/runbook/problems.yaml in nauthera-server.