From d1e8666ac88ad2b732c7f6ca274d856e6c3bef86 Mon Sep 17 00:00:00 2001 From: babolivier Date: Mon, 21 Nov 2022 11:41:11 +0000 Subject: [PATCH] deploy: 640cb3c81c927535a18b85c49a1cc2d856d03c2e --- develop/print.html | 2 +- develop/usage/administration/admin_api/index.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/develop/print.html b/develop/print.html index a4530baa79..1ea2b12ff1 100644 --- a/develop/print.html +++ b/develop/print.html @@ -10888,7 +10888,7 @@ command. This is a script that is distributed as part of synapse. It is possibly already on your $PATH depending on how Synapse was installed.

Finding your user's access_token is client-dependent, but will usually be shown in the client's settings.

Making an Admin API request

-

For security reasons, we recommend +

For security reasons, we recommend that the Admin API (/_synapse/admin/...) should be hidden from public view using a reverse proxy. This means you should typically query the Admin API from a terminal on the machine which runs Synapse.

diff --git a/develop/usage/administration/admin_api/index.html b/develop/usage/administration/admin_api/index.html index 2b6447abc1..0d5587271d 100644 --- a/develop/usage/administration/admin_api/index.html +++ b/develop/usage/administration/admin_api/index.html @@ -159,7 +159,7 @@ command. This is a script that is distributed as part of synapse. It is possibly already on your $PATH depending on how Synapse was installed.

Finding your user's access_token is client-dependent, but will usually be shown in the client's settings.

Making an Admin API request

-

For security reasons, we recommend +

For security reasons, we recommend that the Admin API (/_synapse/admin/...) should be hidden from public view using a reverse proxy. This means you should typically query the Admin API from a terminal on the machine which runs Synapse.