Repository navigation
register_rejects_if_user_already_exists does not account for implementations requiring auth before performing validation #955
Description
TestRegistration/parallel/POST_/register_rejects_if_user_already_exists fails if the homeserver returns a UIA challenge instead of outright rejecting the request due to the duplicate user. Continuwuity, for example, still rejects the request as expected after completing UIA, but interactive auth is required before it is willing to progress further:
$ curl --json '{"username": "nex", "password": "hello world"}' 10.11.10.134:8008/_matrix/client/v3/register
{"flows":[{"stages":["m.login.registration_token"]}],"params":{},"session":"redacted"}% $ curl --json '{"username": "nex", "password": "hello world", "auth": {"type": "m.login.registration_token", "token": "redacted", "session": "redacted"}}' 10.11.10.134:8008/_matrix/client/v3/register
{"errcode":"M_USER_IN_USE","error":"Username is not available."}
There's no spec that defines what order these two things should be checked in, so the test should probably try to complete the challenge if it receives one.
Activity
timedoutuk commentedon Nov 4, 2026
Same problem for the special characters test