#2367 RFE: SSSD should preserve case for user uid field.
Closed: Fixed None Opened 6 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1105740

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

RFE Request

0. Proposed title of this feature request
SSSD should preserve case for user.

1. Who is the customer behind the request?


2. What is the nature and description of the request?
sssd is folding names to all lower case when case_sensitive=false. It should
preserve the case as it is configured.

3. Why does the customer need this? (List the business requirements here)
Folding case on names can lead to applications breaking which expect a certain
case.


4. How would the customer like to achieve this? (List the functional
requirements here)
Add a  new value for case_sensitive option true|false|preserving

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
review: True => 0
selected: =>
summary: SSSD should preserve case for user uid field. => RFE: SSSD should preserve case for user uid field.
testsupdated: => 0
type: defect => enhancement

Looks like downstream won't need this RFE too soon, moving to 1.12.1 for now.

milestone: NEEDS_TRIAGE => SSSD 1.12.1

Fields changed

review: 0 => 1

Fields changed

owner: somebody => mzidek

Fields changed

patch: 0 => 1

resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.12.1

3 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3409

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata