Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-04-28 13:24:10 +02:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Don't require servers/clients to support "none"

Browse source
This commit is contained in:
Andrew Morgan 2019-07-23 16:43:55 +01:00
parent 3031df79cc
commit 3b8c57e06c
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
proposals/2134-identity-hash-lookup.md
View file

@ -134,10 +134,11 @@ negotiated by the client and server at their discretion.
There are certain situations when an identity server cannot be expected to There are certain situations when an identity server cannot be expected to
compare hashed 3PID values; for example, when a server is connected to a compare hashed 3PID values; for example, when a server is connected to a
backend provider such as LDAP, it is not efficient for the identity server to backend provider such as LDAP, it is not efficient for the identity server to
pull all of the addresses and hash them on lookup. For this case, clients pull all of the addresses and hash them upon lookup. For this case, can also
and server MUST also support sending plain-text 3PID values. To agree upon support receiving plain-text 3PID addresses from clients. To agree upon this,
this, the `"algorithms"` field of `GET /hash_details` MUST contain the value the value `"none"` can be added to the `"algorithms"` array of `GET
`"none"`. /hash_details`. The client can then choose to send plain-text values by
setting the `"algorithm"` value in `POST /lookup` to `"none"`.
No hashing will be performed if the client and server decide on `"none"`, and No hashing will be performed if the client and server decide on `"none"`, and
3PIDs will be sent in plain-text, similar to the v1 `/lookup` API. When this 3PIDs will be sent in plain-text, similar to the v1 `/lookup` API. When this