View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009818 | 10000-018: Role-Based Security | Spec | public | 2024-09-05 12:42 | 2024-09-26 11:46 |
| Reporter | Matthias Isele | Assigned To | Matthias Damm | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.05.04 RC1 | ||||
| Fixed in Version | 1.05.04 | ||||
| Summary | 0009818: Behaviour of UserManagementType RemoveUser not defined | ||||
| Description | What is the expected behaviour in the server if a user that is currently used (active session) is removed. A similar szenario is described in Part 12 ApplyChanges: For me the logic for a X509 token that is no longer trusted and a user that no longer exists should be the same. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
Agreed in F2F meeting to close the sessions of the user. |
|
|
For RoleType added the following sentence: For ModifyUser added the following sentence: For RemoveUser added the following sentence: |
|
|
Agreed to changes edited in F2F. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-09-05 12:42 | Matthias Isele | New Issue | |
| 2024-09-24 08:32 | Matthias Damm | Assigned To | => Matthias Damm |
| 2024-09-24 08:32 | Matthias Damm | Status | new => assigned |
| 2024-09-24 08:33 | Matthias Damm | Note Added: 0021793 | |
| 2024-09-26 09:20 | Matthias Damm | Status | assigned => resolved |
| 2024-09-26 09:20 | Matthias Damm | Resolution | open => fixed |
| 2024-09-26 09:20 | Matthias Damm | Fixed in Version | => 1.05.04 |
| 2024-09-26 09:20 | Matthias Damm | Note Added: 0021807 | |
| 2024-09-26 11:46 | Jim Luth | Status | resolved => closed |
| 2024-09-26 11:46 | Jim Luth | Note Added: 0021816 |