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

Clarification on IDs

Browse source 
Specifically using the term "virtual user ID" in more places to mean the namespace of AS user IDs.
This commit is contained in:
Kegsay 2015-01-15 16:51:20 +00:00
parent e0e9beebc0
commit 0313397e42
1 changed files with 4 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
drafts/as-http-api.rst
View file

@ -157,8 +157,9 @@ Linking ``[Draft]``
own as anyone who wants to talk to the virtual user will do a lookup before trying
the application service...
Clients may want to link their matrix user ID to their 3PID (e.g. IRC nick). This
API allows the AS to do this, so messages sent from the AS are sent as the client.
Clients may want to link their matrix user ID to their virtual user ID. This
API allows the AS to do this, so messages sent from the AS are sent as the client's
user ID, instead of the virtual user ID.
This is not achieved using OAuth2 or similar because the trust relationships are
different. The application service already has a huge amount of trust from the
@ -191,7 +192,7 @@ To revoke permission for an application service to masquerade as a user:
Inputs:
- Credentials of user (e.g. ``access_token``)
- The user ID within an application service's namespace to revoke. If blank,
revokes all user IDs linked to this matrix user ID.
revokes all virtual user IDs linked to this matrix user ID.
Output:
- None.
Side effects: