wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Reference the server-server specification for /onbind

Browse source
This commit is contained in:
Travis Ralston 2018-08-29 21:01:49 -06:00
parent 0387da51e2
commit dc602b74d2
1 changed files with 4 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

34
specification/identity_service_api.rst
View file

@ -227,36 +227,10 @@ An identity service can store pending invitations to a user's 3pid, which will
be retrieved and can be either notified on or look up when the 3pid is be retrieved and can be either notified on or look up when the 3pid is
associated with a Matrix user ID. associated with a Matrix user ID.
At a later point, if the owner of that particular 3pid binds it with a Matrix user ID, the identity server will attempt to make an HTTP POST to the Matrix user's homeserver which looks roughly as below:: At a later point, if the owner of that particular 3pid binds it with a Matrix user
ID, the identity service will attempt to make an HTTP POST to the Matrix user's
POST https://bar.com:8448/_matrix/federation/v1/3pid/onbind homeserver via the `/3pid/onbind`_ endpoint. The request MUST be signed with a
Content-Type: application/json long-term private key for the identity service.
{
"medium": "email",
"address": "foo@bar.baz",
"mxid": "@alice:example.tld",
"invites": [
{
"medium": "email",
"address": "foo@bar.baz",
"mxid": "@alice:example.tld",
"room_id": "!something:example.tld",
"sender": "@bob:example.tld",
"signed": {
"mxid": "@alice:example.tld",
"signatures": {
"vector.im": {
"ed25519:0": "somesignature"
}
},
"token": "sometoken"
}
}
]
}
Where the signature is produced using a long-term private key.
{{store_invite_is_http_api}} {{store_invite_is_http_api}}