Merge pull request #153 from matrix-org/daniel/3pidyetagain

3pid invites: remove mentions of display_name
pull/977/head
Daniel Wagner-Hall 9 years ago
commit 624756fb9a

@ -84,8 +84,7 @@ paths:
{ {
"id_server": "matrix.org", "id_server": "matrix.org",
"medium": "email", "medium": "email",
"address": "cheeky@monkey.com", "address": "cheeky@monkey.com"
"display_name": "A very cheeky monkey"
} }
properties: properties:
id_server: id_server:
@ -98,10 +97,7 @@ paths:
address: address:
type: string type: string
description: The invitee's third party identifier. description: The invitee's third party identifier.
display_name: required: ["id_server", "medium", "address"]
type: string
description: A user-friendly string describing who has been invited. It should not contain the address of the invitee, to avoid leaking mappings between third party identities and matrix user IDs.
required: ["id_server", "medium", "address", "display_name"]
responses: responses:
200: 200:
description: The user has been invited to join the room. description: The user has been invited to join the room.

@ -127,13 +127,10 @@ It is important for user privacy that leaking the mapping between a matrix user
ID and a third party identifier is hard. In particular, being able to look up ID and a third party identifier is hard. In particular, being able to look up
all third party identifiers from a matrix user ID (and accordingly, being able all third party identifiers from a matrix user ID (and accordingly, being able
to link each third party identifier) should be avoided wherever possible. to link each third party identifier) should be avoided wherever possible.
To this end, when implementing this API care should be taken to avoid To this end, the third party identifier is not put in any event, rather an
adding links between these two identifiers as room events. This mapping can be opaque display name provided by the identity server is put into the events.
unintentionally created by specifying the third party identifier in the Clients should not remember or display third party identifiers from invites,
``display_name`` field of the ``m.room.third_party_invite`` event, and then other than for the use of the inviter themself.
observing which matrix user ID joins the room using that invite. Clients SHOULD
set ``display_name`` to a value other than the third party identifier, e.g. the
invitee's common name.
Homeservers are not required to trust any particular identity server(s). It is Homeservers are not required to trust any particular identity server(s). It is
generally a client's responsibility to decide which identity servers it trusts, generally a client's responsibility to decide which identity servers it trusts,

Loading…
Cancel
Save