Bug #25300
closedOnly remaining user managed by file cannot be deleted
Description
When starting Rudder with only the OIDC provider enabled (properties rudder.auth.provider=oidc
), and when still having other users managed by file,
when attempting to delete the file users from the button, they are successfully removed from the user management interface, except for the last one :
There is a success notification, and the user is no longer in the rudder-users.xml
file. But in the database the user is still present with the active
or disabled
status instead of deleted
.
That user should be marked as deleted in the database and no longer displayed in the main user management interface.
N.B. : there are also another weird behavior : after deleting it (then it the file no longer has users), and creating a new user from the interface, the previous user eventually gets deleted and replaced by the new user 🤯
Files
Updated by Clark ANDRIANASOLO 4 months ago
- Status changed from New to In progress
Updated by Clark ANDRIANASOLO 4 months ago
- Target version changed from 8.2.0~beta1 to 8.1.7
- Priority changed from 45 to 90
This happens since 8.1 even with the old user-management interface, likely since #24344
Updated by Clark ANDRIANASOLO 4 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/5812
Updated by Clark ANDRIANASOLO 4 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|359ca8a97c5d470872db855c75249349f3e328c4.
Updated by Clark ANDRIANASOLO 3 months ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ 2 months ago
- Status changed from Pending release to Released
- Priority changed from 90 to 89
This bug has been fixed in Rudder 8.1.7 which was released today.