Bug 48181 – Not possible to change username in upper-/lowercase

Bug 48181 - Not possible to change username in upper-/lowercase


Summary:	Not possible to change username in upper-/lowercase

Status:	RESOLVED DUPLICATE of bug 52760

Product:	UCS
Classification:	Unclassified
Component:	General
Version:	UCS 4.3
Hardware:	Other other

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-11-19 15:11 CET by Michael Grandjean
Modified:	2021-02-10 21:21 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.046
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael Grandjean

2018-11-19 15:11:55 CET

UCS 4.3-2 Errata 305

It's not possible to "rename" a username from e.g. mixed-case to lowercase:

uid: Michael.Grandjean -> michael.grandjean

The attempt will result in this notification:
"The LDAP object could not be saved: The username is already in use as username or as groupname michael.grandjean"

In most cases the "uid" attribute is case-insensitive, but there are reasons why we want to change the casing:
- Bugs in our and in other software products that are case-sensitive
- Querying the group attribute "uniqueMember" or "memberUid" - there the "uid" is (part of) the value and those ldap queries *are* case sensitive (e.g. memberUid="uid=Michael.Grandjean" != memberUid="uid=michael.grandjean")

Comment 1 Florian Best

2021-02-10 21:21:16 CET


*** This bug has been marked as a duplicate of bug 52760 ***