From cd34d4e19b334c3a8165bb48deaa5adc7085fecd Mon Sep 17 00:00:00 2001 From: Kegan Dougal Date: Wed, 14 Oct 2015 15:12:15 +0100 Subject: [PATCH] SPEC-182: Make it clearer how ASes are supposed to create users by linkifying the right text. --- specification/0-feature_profiles.rst | 2 +- specification/3-application_service_api.rst | 8 +++++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/specification/0-feature_profiles.rst b/specification/0-feature_profiles.rst index b9f12b74..6c11dd2f 100644 --- a/specification/0-feature_profiles.rst +++ b/specification/0-feature_profiles.rst @@ -1,7 +1,7 @@ Feature Profiles ================ -.. sect:feature-profiles: +.. _sect:feature-profiles: Matrix supports many different kinds of clients: from embedded IoT devices to desktop clients. Not all clients can provide the same feature sets as other diff --git a/specification/3-application_service_api.rst b/specification/3-application_service_api.rst index a6e82137..d1799158 100644 --- a/specification/3-application_service_api.rst +++ b/specification/3-application_service_api.rst @@ -94,7 +94,7 @@ API called when: - HS receives an event for an unknown user ID in the AS's namespace, e.g. an invite event to a room. Notes: - - When the AS receives this request, if the user exists, it must create the user via + - When the AS receives this request, if the user exists, it must `create the user`_ via the CS API. - It can also set arbitrary information about the user (e.g. display name, join rooms, etc) using the CS API. @@ -226,6 +226,9 @@ Ordering notes: ] } + +.. _create the user: `sect:asapi-permissions`_ + Client-Server v2 API Extensions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -291,6 +294,9 @@ Notes: Server admin style permissions ++++++++++++++++++++++++++++++ + +.. _sect:asapi-permissions: + The home server needs to give the application service *full control* over its namespace, both for users and for room aliases. This means that the AS should be able to create/edit/delete any room alias in its namespace, as well as