diff options
| author | DeepBlueV7.X <nicolas.werner@hotmail.de> | 2023-03-29 08:37:27 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-03-29 08:37:27 +0000 |
| commit | 753d1d9cde08940edfd3851d230faaf18a2ba1ff (patch) | |
| tree | d9e41dead6c55bd6bc6f9d92242e96d176803e26 /synapse/handlers/federation_event.py | |
| parent | Implement MSC3983 to proxy /keys/claim queries to appservices. (#15314) (diff) | |
| download | synapse-753d1d9cde08940edfd3851d230faaf18a2ba1ff.tar.xz | |
Fix joining rooms you have been unbanned from (#15323)
* Fix joining rooms you have been unbanned from Since forever synapse did not allow you to join a room after you have been unbanned from it over federation. This was not actually because of the unban event not federating. Synapse simply used outdated state to validate the join transition. This skips the validation if we are not in the room and for that reason won't have the current room state. Fixes #1563 Signed-off-by: Nicolas Werner <nicolas.werner@hotmail.de> * Add changelog Signed-off-by: Nicolas Werner <nicolas.werner@hotmail.de> * Update changelog.d/15323.bugfix --------- Signed-off-by: Nicolas Werner <nicolas.werner@hotmail.de>
Diffstat (limited to 'synapse/handlers/federation_event.py')
| -rw-r--r-- | synapse/handlers/federation_event.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/synapse/handlers/federation_event.py b/synapse/handlers/federation_event.py index b7136f8d1c..648843cdbe 100644 --- a/synapse/handlers/federation_event.py +++ b/synapse/handlers/federation_event.py @@ -583,7 +583,7 @@ class FederationEventHandler: await self._check_event_auth(origin, event, context) if context.rejected: - raise SynapseError(400, "Join event was rejected") + raise SynapseError(403, "Join event was rejected") # the remote server is responsible for sending our join event to the rest # of the federation. Indeed, attempting to do so will result in problems |