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

mention that we can send tokens via headers

Browse source
This commit is contained in:
Michael Telatynski 2017-10-27 09:52:53 +01:00
parent cc6b16b63c
commit c2b1b7a10e
No known key found for this signature in database
GPG key ID: 3F879DA5AD802A5E
2 changed files with 3 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

1
changelogs/client_server.rst
View file

@ -95,6 +95,7 @@
- Clarify the relationship between ``username`` and ``user_id`` in the - Clarify the relationship between ``username`` and ``user_id`` in the
``/register`` API ``/register`` API
(`#1032 <https://github.com/matrix-org/matrix-doc/pull/1032>`_). (`#1032 <https://github.com/matrix-org/matrix-doc/pull/1032>`_).
- Add mention of ability to send Access Token via an Authorization Header.
r0.2.0 r0.2.0
====== ======

4
specification/client_server_api.rst
View file

@ -171,8 +171,8 @@ Client Authentication
Most API endpoints require the user to identify themselves by presenting Most API endpoints require the user to identify themselves by presenting
previously obtained credentials in the form of an ``access_token`` query previously obtained credentials in the form of an ``access_token`` query
parameter. An access token is typically obtained via the `Login`_ or parameter or through an Authorization Header of ``Bearer $access_token``.
`Registration`_ processes. An access token is typically obtained via the `Login`_ or `Registration`_ processes.
When credentials are required but missing or invalid, the HTTP call will When credentials are required but missing or invalid, the HTTP call will
return with a status of 401 and the error code, ``M_MISSING_TOKEN`` or return with a status of 401 and the error code, ``M_MISSING_TOKEN`` or