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

already_enrolled

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

The user already has the second factor they are trying to enrol (409).

Meaning

An MFA enrolment endpoint under /v1/auth/mfa/ was called for an account that already has an active second factor of that kind, for example a second TOTP authenticator.

Impact

Nothing changed; the existing factor keeps working. A user sees it after enrolling twice in two tabs or by going back in the browser. It is harmless.

Diagnosis

Look the request id up on the Troubleshooting page; the record carries cause already_enrolled. The user's factors are listed by GET /v1/auth/mfa in their own session.

Mitigation

  • As a user: use the factor you have, or remove it from your security settings and enrol again.
  • As a client developer: read the factor status before offering enrolment.

Escalation

Escalate when a user with no active factor gets it. Open an issue with the request id and the server version. Never attach seeds or codes.

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