gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: gnunet
Subject: [taler-docs] branch master updated: -clarify kyc info
Date: Sat, 22 Apr 2023 22:46:01 +0200

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 e65ee88  -clarify kyc info
e65ee88 is described below

commit e65ee88b305318a680627e559661535be3d92603
Author: Florian Dold <florian@dold.me>
AuthorDate: Sat Apr 22 22:45:53 2023 +0200

    -clarify kyc info
---
 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 f1a5101..5eecb8c 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 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/info";
+  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";
 
 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.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]