mirror of
https://github.com/matrix-org/matrix-spec
synced 2026-02-25 07:23:42 +01:00
missing word
This commit is contained in:
parent
c6dd5951a1
commit
da876bb340
|
|
@ -137,11 +137,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 upon lookup. For this case, can also
|
pull all of the addresses and hash them upon lookup. For this case, identity
|
||||||
support receiving plain-text 3PID addresses from clients. To agree upon this,
|
servers can also support receiving plain-text 3PID addresses from clients. To
|
||||||
the value `"none"` can be added to the `"algorithms"` array of `GET
|
agree upon this, the value `"none"` can be added to the `"algorithms"` array
|
||||||
/hash_details`. The client can then choose to send plain-text values by
|
of `GET /hash_details`. The client can then choose to send plain-text values
|
||||||
setting the `"algorithm"` value in `POST /lookup` to `"none"`.
|
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
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue