View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009048 | Taler | exchange | public | 2024-08-08 10:45 | 2025-05-08 21:37 |
| Reporter | Christian Grothoff | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | confirmed | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | post-1.0 | ||||
| Summary | 0009048: introduce a default check and support vATTEST API [4h] | ||||
| Description | A check with the "check_name" of "default" should be configured. This check is used when users inquire about KYC in the original state before any trigger thresholds have been passed. This would require: 1) a new endpoint to allow users to get their access token based only on their (h_)payto -- as kyc-check requires a requirement row. 2) changes to the /kyc-info/ endpoint to return the default check if there is no requirement for the given account/access token 3) documentation updates This would enable users to do *voluntary* KYC. See *vATTEST*. | ||||
| Tags | security | ||||
| has duplicate | 0009879 | confirmed | voluntary measures not implemented |
|
|
Relevant previous kyc_logic.c API code fragment (currently removed): { const struct TALER_KYCLOGIC_KycCheck *check; check = find_check ("default"); if (NULL == check) { GNUNET_log (GNUNET_ERROR_TYPE_WARNING, "A 'default' check should be defined\n"); } } |
|
|
(1) is done with the latest change to the kyc-check endpoint now using h_payto instead of a requirement row. |
|
|
We now have *voluntary* *measures*. (That can be set as such in the configuration.) That seems saner than 'default checks'. |
|
|
we need to distinguish required nothing-left and you may do something if you want in the KYC-info status for the merchant SPA so that the merchant spa shows the KYC link. Right now, we only have 'ready' (nothing to be done) and 'kyc-required', nothing for 'optional'. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-08-08 10:45 | Christian Grothoff | New Issue | |
| 2024-08-08 10:45 | Christian Grothoff | Status | new => assigned |
| 2024-08-08 10:45 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2024-08-08 10:45 | Christian Grothoff | Note Added: 0022952 | |
| 2024-08-08 10:46 | Christian Grothoff | Summary | introduce a default check => introduce a default check and support vATTEST API |
| 2024-08-08 10:50 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2024-08-08 10:50 | Christian Grothoff | Status | assigned => confirmed |
| 2024-09-03 01:11 | Christian Grothoff | Note Added: 0023146 | |
| 2024-09-03 01:11 | Christian Grothoff | Target Version | post-1.0 => 0.14 |
| 2024-09-03 01:11 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2024-09-03 01:11 | Christian Grothoff | Status | confirmed => assigned |
| 2024-09-04 23:26 | Christian Grothoff | Summary | introduce a default check and support vATTEST API => introduce a default check and support vATTEST API [4h] |
| 2024-09-05 11:57 | Christian Grothoff | Note Added: 0023165 | |
| 2024-09-05 13:38 | Christian Grothoff | Target Version | 0.14 => post-1.0 |
| 2024-09-05 13:45 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2024-09-05 13:45 | Christian Grothoff | Status | assigned => confirmed |
| 2024-09-16 23:47 | Christian Grothoff | Target Version | post-1.0 => 1.2 |
| 2025-04-17 22:46 | Christian Grothoff | Tag Attached: security | |
| 2025-04-17 22:46 | Christian Grothoff | Target Version | 1.2 => post-1.0 |
| 2025-04-21 22:01 | Christian Grothoff | Note Added: 0024644 | |
| 2025-05-08 21:37 | Christian Grothoff | Relationship added | has duplicate 0009879 |
