View Issue Details

IDProjectCategoryView StatusLast Update
0006646libeufinlibeufin-nexuspublic2023-01-08 10:32
ReporterMS Assigned ToMS  
PriorityhighSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Target Version0.9.0Fixed in Version0.9.0 
Summary0006646: Multiple bank connections with the same name for ONE user should not be allowed.
DescriptionSee summary.
TagsNo tags attached.

Activities

MS

2020-11-13 17:25

manager   ~0017127

This can be as well observed when restoring a connection backup: nexus writes the restored connection in the database without checking if another connection with the same name exists first. Result: two connections with the same name are in the database.

MS

2021-01-19 12:14

manager   ~0017372

This commit: 73672682cd5cce06a6e4132748132b77f3a3f50, fixes this issue (and it allows to reuse a connection name for different users).

MS

2021-01-19 16:58

manager   ~0017373

After private discussion, it emerged that Nexus is not supposed (at least for the moment) to provide a "full isolation" between users. Therefore, every connection name is global (= not usable by more than one user.)

Issue History

Date Modified Username Field Change
2020-11-13 16:19 MS New Issue
2020-11-13 16:19 MS Target Version => 0.9.2
2020-11-13 17:25 MS Note Added: 0017127
2021-01-14 00:21 Florian Dold Assigned To => MS
2021-01-14 00:21 Florian Dold Status new => assigned
2021-01-14 00:21 Florian Dold Priority normal => high
2021-01-19 12:14 MS Note Added: 0017372
2021-01-19 12:14 MS Status assigned => resolved
2021-01-19 12:14 MS Resolution open => fixed
2021-01-19 16:58 MS Note Added: 0017373
2023-01-08 10:31 Christian Grothoff Fixed in Version => 0.9.0
2023-01-08 10:31 Christian Grothoff Target Version 0.9.2 => 0.9.0
2023-01-08 10:32 Christian Grothoff Status resolved => closed
2023-04-13 20:38 Florian Dold Category nexus => libeufin-nexus