Second-factor code
What the Screen Is For
Answer an authenticator-app challenge belonging to the current sign-in attempt.
What It Shows and Lets People Do
The page consumes the retained sign-in challenge and submits the authenticator code. It navigates to the safe return destination after successful authentication.
States and Errors
Code-length validation is local, while a rejected provider code appears as a form alert. Without a usable retained challenge the visitor must restart sign-in.
The state rows describe observed loading, empty, refusal or inactive handling where present. Linked validation rules belong to the planning layer; client feedback and authoritative service checks have distinct responsibilities.
Patterns It Must Respect
The pattern list names the built shared components and interaction patterns checked for this screen. This contract describes the existing screen; it supplies no replacement visual design.