mirror of
https://mau.dev/maunium/synapse.git
synced 2024-10-01 01:36:05 -04:00
1168cbd54d
When a server sends a third party invite another server may be the one that the inviting user registers with. In this case it is that remote server that will issue an actual invitation, and wants to do it "in the name of" the original invitee. However, the new proper invite will not be signed by the original server, and thus other servers would reject the invite if it was seen as coming from the original user. To fix this, a special case has been added to the auth rules whereby another server can send an invite "in the name of" another server's user, so long as that user had previously issued a third party invite that is now being accepted. |
||
---|---|---|
.. | ||
__init__.py | ||
_base.py | ||
account_data.py | ||
admin.py | ||
appservice.py | ||
auth.py | ||
device.py | ||
devicemessage.py | ||
directory.py | ||
e2e_keys.py | ||
events.py | ||
federation.py | ||
identity.py | ||
message.py | ||
presence.py | ||
profile.py | ||
receipts.py | ||
register.py | ||
room_list.py | ||
room_member.py | ||
room.py | ||
search.py | ||
sync.py | ||
typing.py |