Merge pull request #2037 from matrix-org/travis/1.0/appservice-hs-token
Clarify how homeservers are meant to auth themselves to appservices
This commit is contained in:
commit
76829ad988
2 changed files with 10 additions and 0 deletions
|
@ -0,0 +1 @@
|
||||||
|
Add missing definition for how appservices verify requests came from a homeserver.
|
|
@ -187,6 +187,15 @@ An example registration file for an IRC-bridging application service is below:
|
||||||
Homeserver -> Application Service API
|
Homeserver -> Application Service API
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
Authorization
|
||||||
|
+++++++++++++
|
||||||
|
|
||||||
|
Homeservers MUST include a query parameter named ``access_token`` containing the
|
||||||
|
``hs_token`` from the application service's registration when making requests to
|
||||||
|
the application service. Application services MUST verify the provided ``access_token``
|
||||||
|
matches their known ``hs_token``, failing the request with a ``M_FORBIDDEN`` error
|
||||||
|
if it does not match.
|
||||||
|
|
||||||
Legacy routes
|
Legacy routes
|
||||||
+++++++++++++
|
+++++++++++++
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue