Files
matrix-authentication-service/crates
Quentin Gliech 815cc9c1e5 Enforce invite code constraints server-side when registering
The registration form only ever used the invite code to attach it to the
registration: an invalid or revoked code was silently ignored, and the
username and email address a code was issued for were only enforced by the
`readOnly` attribute on the client side.

Resolve the code up front instead, so that:

 - an unknown, revoked, expired or exhausted code is rejected with an error
   on the field, and re-rendering the form keeps the code
 - a code which imposes a username or an email address only lets that
   identity register
 - a `passwordless` code skips the password entirely, and requires an email
   address to verify even when the server otherwise does not

The code is also consumed whenever one was used, not only when the server
requires one.
2026-09-10 18:53:59 +02:00
..
2026-05-21 16:44:20 -05:00
2026-05-21 16:37:47 -05:00
2026-05-21 16:44:20 -05:00
2026-05-21 16:37:47 -05:00
2026-05-21 16:37:47 -05:00
2026-05-21 16:37:47 -05:00
2026-05-21 16:45:56 -05:00