This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Switch to Identity Service API v2 #9677
Labels
A-Spec-Compliance
places where synapse does not conform to the spec
O-Occasional
Affects or can be seen by some users regularly or most users rarely
S-Major
Major functionality / product severely impaired, no satisfactory workaround.
T-Task
Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
Z-Future-Maintenance
Things that can't yet be done, but will need cleaning up in a couple of months/releases
Milestone
The v1 Identity Service API will be dropped from the spec soon. There are a number of places where we still use v1 APIs, where we should instead first try v2, then fall back to v1.
synapse/synapse/handlers/identity.py
Lines 124 to 137 in e550ab1
synapse/synapse/handlers/identity.py
Lines 273 to 279 in 0a00b7f
synapse/synapse/handlers/identity.py
Lines 446 to 456 in 0a00b7f
synapse/synapse/handlers/identity.py
Lines 499 to 508 in 0a00b7f
synapse/synapse/handlers/identity.py
Lines 586 to 595 in 0a00b7f
I believe we also store IS URLs (
/_matrix/identity/api/v1/pubkey/[ephemeral/]isvalid
) in third-party invite state events, which will eventually fail once IS's dropv1
APIs. Edit: Yes, we do:Update 2022/06/24: It's also worth noting that we use the v1
/store-invite
andpubkey/isvalid
APIs when clients send a 3pid invite with noid_access_token
, which we need to disable:synapse/synapse/handlers/identity.py
Lines 893 to 911 in d549099
The text was updated successfully, but these errors were encountered: