View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008642 | Taler | specification | public | 2024-03-14 12:30 | 2025-04-23 22:30 |
| Reporter | sebasjm | Assigned To | Resolution deadline | ||
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | text | Reproducibility | always |
| Status | implementing | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0008642: design document for extend access token API | ||||
| Description | feature that I think are a must: token scope (the token I give to the merchant backend should not be able to read my account info ) user should be able to invalidate the session acc token specifically feature that I think are a good to have: seeing all the active sessions access tokens (how many devices can possible access) seeing info about the session access token (last ip, last active time, device) | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-03-14 12:30 | sebasjm | New Issue | |
| 2024-03-14 12:30 | sebasjm | Status | new => assigned |
| 2024-03-14 12:30 | sebasjm | Assigned To | => sebasjm |
| 2024-07-28 20:01 | Christian Grothoff | Severity | major => text |
| 2025-04-23 22:30 | Christian Grothoff | Assigned To | sebasjm => |
| 2025-04-23 22:30 | Christian Grothoff | Status | assigned => implementing |