View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009644 | Taler | libeufin-bank-ui (SPA) | public | 2025-03-20 20:11 | 2025-06-25 00:44 |
| Reporter | sebasjm | Assigned To | |||
| Priority | low | Severity | feature | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Product Version | git (master) | ||||
| Target Version | post-1.0 | ||||
| Summary | 0009644: bank ui should support listing and revoking tokens | ||||
| Description | the api is implemented https://docs.taler.net/core/api-corebank.html#get--accounts-$USERNAME-tokens but the spa doesn't use that | ||||
| Tags | security | ||||
| related to | 0009523 | confirmed | Allow connecting the merchant backend to the bank revenue API via token in URI | |
| related to | 0010118 | assigned | Christian Grothoff | merchant backend should have API to list and revoke access tokens |
| related to | 0010108 | feedback | Christian Grothoff | customer unable to extract authorization token for WooCommerce integration |
|
|
please prioritize, the only important use case for this (i can think of) is: if the customer doesn't have access to the merchant backoffice and want's to remove access to the revenue API. The token description should be enough to identify which token is. |
|
|
Indeed, not a high priority right now. |
|
|
See related merchant issues that the Bank API does not actually return the token value rn. |
|
|
the API to list tokens must not return the token values, it should return a reference id to delete them and an description to identify then (AFAIK last access, creation, description, scopes) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-03-20 20:11 | sebasjm | New Issue | |
| 2025-03-20 20:11 | sebasjm | Status | new => assigned |
| 2025-03-20 20:11 | sebasjm | Assigned To | => sebasjm |
| 2025-03-20 20:21 | sebasjm | Assigned To | sebasjm => Christian Grothoff |
| 2025-03-20 20:21 | sebasjm | Status | assigned => feedback |
| 2025-03-20 20:21 | sebasjm | Note Added: 0024266 | |
| 2025-03-21 01:48 | Christian Grothoff | Priority | normal => low |
| 2025-03-21 01:48 | Christian Grothoff | Severity | major => feature |
| 2025-03-21 01:48 | Christian Grothoff | Target Version | 1.0 => post-1.0 |
| 2025-03-21 01:48 | Christian Grothoff | Note Added: 0024267 | |
| 2025-03-21 01:48 | Christian Grothoff | Assigned To | Christian Grothoff => sebasjm |
| 2025-04-24 01:25 | Christian Grothoff | Assigned To | sebasjm => |
| 2025-04-24 01:25 | Christian Grothoff | Status | feedback => confirmed |
| 2025-04-24 01:25 | Christian Grothoff | Tag Attached: security | |
| 2025-04-28 08:46 | Christian Grothoff | Relationship added | related to 0009523 |
| 2025-06-21 21:18 | Christian Grothoff | Relationship added | related to 0010118 |
| 2025-06-24 22:27 | schanzen | Relationship added | related to 0010108 |
| 2025-06-24 22:33 | schanzen | Note Added: 0025353 | |
| 2025-06-25 00:44 | sebasjm | Note Added: 0025357 |
