-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Synapse accepts "user" instead of "username" in application service /register #9547
Comments
This may be related to old client behaviour, in which case changing it would be hard. |
possibly, but it would have to be very old clients, and tbh we should be doing a better job at deprecating and sunsetting these things. |
I'm assuming that this accepts both since sytest still passes? So this is really a matter of deprecating the old |
@clokep Yep. We need to do a similar thing to #9559 / #9548 here. Create a deprecation notice in the changelog and then remove the old support once enough time has passed. Someone needs to do the investigation on whether anyone is still using |
@Half-Shot / @tulir Any idea if we can deprecate and remove this (similar to the legacy AS paths)? |
And for all avoidance of doubt that this is really old:
So this was way before r0.1.0 of the appservice spec. I'm going to do a PR to deprecate this and we can remove it in the future. |
This is deprecated and can be removed in v1.88.0. Since this was never specced I think we can just remove it. |
Description
When an AS registers a user in Synapse, it seems happy to accept
"user"
instead of the specced"username"
in the request body.This is related to matrix-org/sytest#1017.
Steps to reproduce
Up until matrix-org/sytest@ab7b8f0, Sytest was testing this way and the tests passed.
Version information
The text was updated successfully, but these errors were encountered: