From 3b8c57e06ca961c6842ab409b64f825b8884c573 Mon Sep 17 00:00:00 2001 From: Andrew Morgan Date: Tue, 23 Jul 2019 16:43:55 +0100 Subject: [PATCH] Don't require servers/clients to support "none" --- proposals/2134-identity-hash-lookup.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/proposals/2134-identity-hash-lookup.md b/proposals/2134-identity-hash-lookup.md index d6cb0506..b40f9f28 100644 --- a/proposals/2134-identity-hash-lookup.md +++ b/proposals/2134-identity-hash-lookup.md @@ -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 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 -pull all of the addresses and hash them on lookup. For this case, clients -and server MUST also support sending plain-text 3PID values. To agree upon -this, the `"algorithms"` field of `GET /hash_details` MUST contain the value -`"none"`. +pull all of the addresses and hash them upon lookup. For this case, can also +support receiving plain-text 3PID addresses from clients. To agree upon this, +the value `"none"` can be added to the `"algorithms"` array of `GET +/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 3PIDs will be sent in plain-text, similar to the v1 `/lookup` API. When this