You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Complement calls /_matrix/client/r0/register with an empty access_token query parameter, which causes Synapse to fail the request. It is valid to call /register with an access token if you're an application service registering a user in your namespace.
=== CONT TestRegistration/parallel/POST_/register_returns_the_same_device_id_as_that_in_the_request
client.go:196: Making POST request to http://localhost:32857/_matrix/client/r0/register?access_token=
client.go:196: Request body: {"auth":{"type":"m.login.dummy"},"username":"user-device","password":"sUp3rs3kr1t","device_id":"my_device_id"}
=== CONT TestRegistration
client.go:262: POST /_matrix/client/r0/register => 401 Unauthorized (1.981009ms)
=== CONT TestRegistration/parallel/POST_/register_returns_the_same_device_id_as_that_in_the_request
client.go:196: HTTP/1.1 401 Unauthorized
Transfer-Encoding: chunked
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, Authorization
Access-Control-Allow-Methods: GET, HEAD, POST, PUT, DELETE, OPTIONS
Access-Control-Allow-Origin: *
Cache-Control: no-cache, no-store, must-revalidate
Content-Type: application/json
Date: Wed, 04 Nov 2020 16:53:03 GMT
Server: Synapse/1.22.1
55
{"errcode":"M_UNKNOWN_TOKEN","error":"Unrecognised access token","soft_logout":false}
0
apidoc_register_test.go:92: CSAPI.MustDo POST http://localhost:32857/_matrix/client/r0/register?access_token= returned HTTP 401
The question of whether Synapse should just ignore an empty access_token query parameter is a good one. The spec doesn't really say one way or the other, so it's probably not good to fail a homeserver for this. Though I'm not sure where using an empty access_token would even be valid either.
Just wanted to get your thoughts on whether you think this should be solved Synapse-side or Complement-side.
The text was updated successfully, but these errors were encountered:
Complement calls
/_matrix/client/r0/register
with an emptyaccess_token
query parameter, which causes Synapse to fail the request. It is valid to call/register
with an access token if you're an application service registering a user in your namespace.The question of whether Synapse should just ignore an empty
access_token
query parameter is a good one. The spec doesn't really say one way or the other, so it's probably not good to fail a homeserver for this. Though I'm not sure where using an emptyaccess_token
would even be valid either.Just wanted to get your thoughts on whether you think this should be solved Synapse-side or Complement-side.
The text was updated successfully, but these errors were encountered: