taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 388aefffc9d2941b64542001a4277bc56b8daacb
parent 8a3c524ffcaad7e45da6b3336da0c2010cc33d0d
Author: Christian Grothoff <christian@grothoff.org>
Date:   Thu, 12 Sep 2024 15:32:41 +0200

remove unused CONVERTER option (fixes #9126)

Diffstat:
Mdesign-documents/023-taler-kyc.rst | 12------------
Mmanpages/taler.conf.5.rst | 12------------
Mtaler-kyc-manual.rst | 14+-------------
3 files changed, 1 insertion(+), 37 deletions(-)

diff --git a/design-documents/023-taler-kyc.rst b/design-documents/023-taler-kyc.rst @@ -940,18 +940,6 @@ description of the high-level process for different providers. # Which plugin is responsible for this provider? LOGIC = PLUGIN_NAME - # Name of a program to run on the output of the plugin - # to convert the result into the desired set of attributes. - # The converter must create a log for the system administrator - # if the provided inputs do not match expectations. - # Note that the converter will be expected to output the - # set of attributes listed under the respective ``[kyc-check-*]`` - # sections. Calling the converter with ``--list-outputs`` - # should generate a (newline-separated) list of attributes - # the converter promises to generate in its JSON output - # (when run regularly). - CONVERTER = taler-exchange-helper-$NAME - # Plus additional logic-specific options, e.g.: AUTHORIZATION_TOKEN = superdupersecret diff --git a/manpages/taler.conf.5.rst b/manpages/taler.conf.5.rst @@ -255,18 +255,6 @@ The following options must be in the section "[kyc-provider-$PROVIDER_NAME]" sec LOGIC API type of the KYC provider. -CONVERTER - Name of a program to run on the output of the plugin - to convert the result into the desired set of attributes. - The converter must create a log for the system administrator - if the provided inputs do not match expectations. - Note that the converter will be expected to output the - set of attributes listed under the respective ``[kyc-check-*]`` - sections. Calling the converter with ``-o`` - should generate a (newline-separated) list of attributes - the converter promises to generate in its JSON output - (when run regularly). - Additional logic-specific options may be given in the section. diff --git a/taler-kyc-manual.rst b/taler-kyc-manual.rst @@ -206,18 +206,6 @@ section. The names of the configuration sections must being with # Choices include "oauth2", "kycaid" and "persona". LOGIC = oauth2 - # Name of a program to run on the output of the plugin - # to convert the result into the desired set of attributes. - # The converter must create a log for the system administrator - # if the provided inputs do not match expectations. - # Note that the converter will be expected to output the - # set of attributes listed under the respective ``[kyc-check-*]`` - # sections. Calling the converter with ``-o`` - # should generate a (newline-separated) list of attributes - # the converter promises to generate in its JSON output - # (when run regularly). - CONVERTER = taler-exchange-helper-$NAME - # Plus additional logic-specific options, e.g.: AUTHORIZATION_TOKEN = superdupersecret @@ -539,7 +527,7 @@ The external providers are expected to yield KYC attributes in the form of key-value pairs where the list of key is defined in the GANA ``gnu-taler-kyc-attributes`` registry, which also defines the format of each attribute. External providers may not directly yield attributes using the -correct encodings, thus CONVERTER programs are typically used to convert +correct encodings, thus converter helper programs are typically used to convert external attribute data into the standardized format.