View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008079 | Taler | exchange | public | 2024-01-12 15:41 | 2024-04-08 01:08 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | ||
| Priority | high | Severity | major | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 0.11 | ||||
| Summary | 0008079: cannot restart KYC process after KYC data was declined by KYC provider | ||||
| Description | ... also, exchange still sees the process as not 'finished' in the database, even though the KYC provider is on the final 'rejected' state (seen with KYCAID). | ||||
| Tags | No tags attached. | ||||
| parent of | 0008708 | assigned | Florian Dold | wallet-core should poll on KYC status [2h] |
| related to | 0008055 | closed | Christian Grothoff | 'finished' in legitimization_processes remains 'false' after KYC process is complete [2d] |
| child of | 0007681 | assigned | Christian Grothoff | demo doesn't have any KYC checks [2d] |
| Not all the children of this issue are yet resolved or closed. | ||||
|
|
While 0008055 *might* have fixed this for KYCAID (still to be tested!), the issue is also very real with Challenger/OAuth2. Here, extra fun is that we get no notification of the ultimate failure state. Should discuss with Martin if we're doing this "wrong" and/or how to do it right. |
|
|
Fixed challenger to provide us an update when the process failed. The exchange now properly re-starts a fresh KYC process when the previous one has ultimately failed. However, the *wallet-core* never refreshes the KYC link, so even if a KYC process has ultimately failed, the wallet will always provide the (stale) link to the original KYC process -- even when 'refresh' is explicitly selected. Wallet-core thus needs to (1) long-poll to learn about KYC status updates *and* (2) if it does get a new KYC URL, actually provide that new link to the GUIs. |
|
|
Note that in the new KYC design, wallet-core will NOT HAVE TO refresh the KYC link, as it will be *stable*. So this is now an exchange-issue, not a wallet-core issue. |
|
|
What about the long-polling? That's still relevant, no? |
|
|
Yes, long-polling you should do. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-01-12 15:41 | Christian Grothoff | New Issue | |
| 2024-01-12 15:41 | Christian Grothoff | Status | new => assigned |
| 2024-01-12 15:41 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2024-01-12 16:54 | Christian Grothoff | Relationship added | related to 0008055 |
| 2024-01-18 23:38 | Christian Grothoff | Relationship added | child of 0007681 |
| 2024-02-06 01:36 | Christian Grothoff | Summary | cannot restart KYC process after KYC data was declined by KYC provider => cannot restart KYC process after KYC data was declined by KYC provider [2d] |
| 2024-02-14 14:31 | Christian Grothoff | Note Added: 0021292 | |
| 2024-02-18 13:23 | Christian Grothoff | Note Added: 0021339 | |
| 2024-02-18 13:23 | Christian Grothoff | Assigned To | Christian Grothoff => Florian Dold |
| 2024-02-18 23:07 | Christian Grothoff | Summary | cannot restart KYC process after KYC data was declined by KYC provider [2d] => cannot restart KYC process after KYC data was declined by KYC provider |
| 2024-04-07 20:29 | Florian Dold | Status | assigned => confirmed |
| 2024-04-07 20:29 | Florian Dold | Relationship added | parent of 0008708 |
| 2024-04-07 20:31 | Christian Grothoff | Note Added: 0022136 | |
| 2024-04-07 20:31 | Christian Grothoff | Assigned To | Florian Dold => Christian Grothoff |
| 2024-04-07 20:31 | Christian Grothoff | Status | confirmed => assigned |
| 2024-04-07 20:42 | Florian Dold | Note Added: 0022138 | |
| 2024-04-08 01:08 | Christian Grothoff | Note Added: 0022141 |
