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_conflict

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

The account could not be created with this address (409).

Meaning

POST /v1/auth/register answers this when the address is already taken in the organization, or is one of the reserved bootstrap administrator addresses. The answer does not say which field or rule collided.

Impact

The visitor cannot register with this address. A person who already has an account sees it when they meant to sign in. Attempts to claim a bootstrap administrator address are an escalation attempt and are recorded as such.

Diagnosis

Look the request id up on the Troubleshooting page. The attempt is recorded as auth.registration.completed with reason conflict and cause identifier_taken or reserved_identifier.

Mitigation

  • As a user: sign in instead, or use "Forgot password". Support should give the same advice to anyone who asks, without confirming whether the address has an account.
  • As an operator: investigate repeated reserved_identifier attempts as an attack.

Escalation

Escalate when a new, unused address is refused. Open an issue with the request id, the audit cause and the server version. Never attach the address in a public issue.

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