Actions
Bug #24955
closed
One user is created each case change even if case sensivity if false
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
When we set case sensitivity to false in rudder-users.xml, we expect to be able to have other case provided by OIDC auto-provisioning, or be able to change the case in the file without having new user created in the base.
This is not the case: one user is created:
- when I try to connect with OIDC providing an other case (and with auto provisioning set to true)
- when I change the case of the user in the file and reload it from plugin UI
Moreover,
Files
Updated by François ARMAND 6 months ago
- Related to Bug #24839: We cannot login with a user login containing uppercase letter if the option case-sensitivity is set to false added
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 8.1.3 to 8.1.4
Updated by Vincent MEMBRÉ 5 months ago
- Target version changed from 8.1.4 to 8.1.5
Updated by Vincent MEMBRÉ 5 months ago
- Target version changed from 8.1.5 to 8.1.6
Updated by Vincent MEMBRÉ 4 months ago
- Target version changed from 8.1.6 to 8.1.7
Updated by Clark ANDRIANASOLO 3 months ago
- Status changed from New to In progress
- Assignee set to Clark ANDRIANASOLO
Updated by Clark ANDRIANASOLO 3 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/5819
Updated by Clark ANDRIANASOLO 3 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|dba23d5de59e31d3c31b9551a5cfd6f041c2ed50.
Updated by Clark ANDRIANASOLO 2 months ago
Checked with
case-sensitivity="false" :
- user login from OIDC now works with the already existing user without consideration of the case, it will not create new users in the database
- also when renaming an existing user to the same one with a different case in the
rudder-users.xmlfile, I can still log in using any case variant, and the database will keep an unique user (the very first one)
There is a caveat though, but it has not caused any issue : the usersessions table contains the different version of the user
userid | sessionid | creationdate | authmethod | permissions | authz | tenants | enddate | endcause
------------------------------+----------------------------------+----------------------------+------------+-------------------------------+--------------+---------+----------------------------+-----------------------
clark.andrianasolo@rudder.io | node01727aqisnwo3s1v336eexwyk4i0 | 2024-09-19 08:17:47.54+00 | oidc | {rudder_admin(administrator)} | {any_rights} | all | 2024-09-19 08:31:36.584+00 | User asked for logout
clark.andrianasolo@RUDDER.io | node01lhkh7k0yq5qmrvbc19367dh614 | 2024-09-19 08:32:01.049+00 | oidc | {rudder_admin(administrator)} | {any_rights} | all | 2024-09-19 08:40:41.41+00 | User asked for logout
clark.andrianasolo@RUDDER.io | node0ado6rpnt4scjb8n4ru2g1pxw24 | 2024-09-19 08:42:04.196+00 | oidc | {rudder_admin(administrator)} | {any_rights} | all | |
Updated by Clark ANDRIANASOLO 2 months ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 2 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.1.7 which was released today.
Actions