From 8da3a557fea47475b6670baec864e9c14f5345f0 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Sun, 22 Nov 2020 05:44:48 -0500 Subject: mark up ‘/private/’ (two instances) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-manual.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'taler-merchant-manual.rst') diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst index 1ab0c913..d03c9aaf 100644 --- a/taler-merchant-manual.rst +++ b/taler-merchant-manual.rst @@ -994,7 +994,7 @@ setup access control! Access control -------------- -All endpoints with /private/ in the URL must be restricted to authorized users +All endpoints with ``/private/`` in the URL must be restricted to authorized users of the respective instance. Specifically, the HTTP server must be configured to only allow access to ``$BASE_URL/private/`` to the authorized users of the default instance, and to ``$BASE_URL/instances/$ID/private/`` to the @@ -1004,7 +1004,7 @@ How access control is done (TLS client authentication, HTTP basic or digest authentication, etc.) is completely up to the merchant and does not matter to the Taler merchant backend. -Note that all of the other endpoints (without /private/) are expected to be +Note that all of the other endpoints (without ``/private/``) are expected to be fully exposed to the Internet, and wallets may have to interact with those endpoints directly without client authentication. -- cgit v1.2.3