View Issue Details

IDProjectCategoryView StatusLast Update
0008604Talermerchant backoffice SPApublic2024-05-15 18:01
ReporterFlorian Dold Assigned Tosebasjm  
PriorityhighSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Target Version0.11Fixed in Version0.11 
Summary0008604: problems with login/impersonation
DescriptionWhen creating a new merchant instance via the default instance, it immediately asks for a login token. It's not clear which login token this is supposed to be.

Furthermore, when using the impersonation feature, it *also* asks for a login (without telling which user). But I would expect that the default instance can always impersonate without having to log in again.
TagsNo tags attached.

Relationships

parent of 0008655 closedsebasjm remove all HTTP api, use the new one 

Activities

sebasjm

2024-03-13 19:21

developer   ~0021901

impersonation seems broken when the impersonated has a security token configured, its a regression.

but default instance will not be able to impersonate without the sec token of the impersonated account

Christian Grothoff

2024-03-21 12:40

manager   ~0021959

Last edited: 2024-03-21 12:41

I actually have trouble with just "simpler" functionalities --- like password changes. Maybe we should *disable* (= hide button/widget) impersonation and keep it as a post-1.0 feature?

Florian Dold

2024-03-27 15:32

manager   ~0022010

We should *hide* the impersonation feature for 0.10 and create a post-1.0 bug to re-add impersonation.

sebasjm

2024-04-05 23:17

developer   ~0022131

the only way to do impersonation is clicking the instance's name link in the instance list (from admin view).

link was removed, now the instance's name is not clickable, effectively removing the feature.

I moving this ticket to 0.11 to enable it again after more testing.

sebasjm

2024-04-05 23:18

developer   ~0022132

commit a9606b04f

sebasjm

2024-04-15 17:01

developer   ~0022246

a7c8f0f3e

Issue History

Date Modified Username Field Change
2024-03-08 18:40 Florian Dold New Issue
2024-03-08 18:40 Florian Dold Status new => assigned
2024-03-08 18:40 Florian Dold Assigned To => sebasjm
2024-03-08 20:33 Florian Dold Severity minor => major
2024-03-13 19:21 sebasjm Note Added: 0021901
2024-03-13 19:21 sebasjm Status assigned => confirmed
2024-03-21 03:19 sebasjm Relationship added parent of 0008655
2024-03-21 12:40 Christian Grothoff Note Added: 0021959
2024-03-21 12:41 Christian Grothoff Note Edited: 0021959
2024-03-27 15:10 Florian Dold Target Version 0.10 => post-1.0
2024-03-27 15:32 Florian Dold Target Version post-1.0 => 0.10
2024-03-27 15:32 Florian Dold Note Added: 0022010
2024-04-03 18:50 sebasjm Priority normal => high
2024-04-05 23:17 sebasjm Note Added: 0022131
2024-04-05 23:18 sebasjm Note Added: 0022132
2024-04-05 23:18 sebasjm Target Version 0.10 => 0.11
2024-04-15 17:01 sebasjm Status confirmed => resolved
2024-04-15 17:01 sebasjm Resolution open => fixed
2024-04-15 17:01 sebasjm Note Added: 0022246
2024-05-15 17:53 Christian Grothoff Fixed in Version => 0.11
2024-05-15 18:01 Christian Grothoff Status resolved => closed