[taler-docs] branch master updated: -clarify kyc info again

[gnunet]

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 615dc5f  -clarify kyc info again
615dc5f is described below

commit 615dc5fe65bb9db5ed831f3deb7d1e757ebaf06a
Author: Florian Dold <florian@dold.me>
AuthorDate: Sat Apr 22 22:54:33 2023 +0200

    -clarify kyc info again
---
 manpages/taler.conf.5.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/manpages/taler.conf.5.rst b/manpages/taler.conf.5.rst
index 5eecb8c..032c88c 100644
--- a/manpages/taler.conf.5.rst
+++ b/manpages/taler.conf.5.rst
@@ -189,7 +189,7 @@ KYC_OAUTH2_LOGIN_URL
   URL of the OAuth2 endpoint to be used for KYC checks. The login URL will be 
encoded as part of the 'redirect_uri' argument of the request to the 
KYC_AUTH2_AUTH_URL. Typically, the user will then be redirected to this URL to 
log in. Example: "http://localhost:8888/oauth/v2/login";
 
 KYC_OAUTH2_INFO_URL
-  URL of the endpoint where the OAuth 2.0 token can be used to download the 
user's KYC details. The server will use the access token obtained from the 
KYC_AUTH2_AUTH_URL to show that it is authorized to obtain the details. 
Example: "http://localhost:8888/api/user/me"; or 
"http://localhost:8888/oauth/v2/kycinfo";
+  URL of the OAuth2-protected resource endpoint, where the OAuth 2.0 token can 
be used to download information about the user that has undergone the KYC 
process. The exchange will use the access token obtained from the 
KYC_AUTH2_AUTH_URL to show that it is authorized to obtain the details. 
Example: "http://localhost:8888/api/user/me"; or 
"http://localhost:8888/oauth/v2/info";
 
 KYC_OAUTH2_CLIENT_ID
   Client ID of the exchange when it talks to the KYC OAuth2 endpoint.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.