Learn more about these different git repos.
Other Git URLs
Unfortunately a lot of environments do not follow posix standards on case sensitivity. It would be a good usability enhancement to allow for a domain to be viewed as case sensitive or insensitive.
Replying to [ticket:890 gbarros]:
Viewed or used where? Can you please specify the use case. Are we talking about domain names in the config file or domain suffix (kerberos realm) of the user principal or the domain in terms of the netgroups?
Replying to [comment:1 dpal]:
User and Group names are case insensitive on most LDAP servers. So we should have an option to mark a sssd domain as case insensitive do all our string comparisons in a case-insensitive way and return all user and group names lowercased to the OS.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.7.0
This is becoming a fairly common question from the field. I'm moving to NEEDS_TRIAGE to discuss moving this up to an earlier release.
milestone: SSSD 1.8.0 => NEEDS_TRIAGE rhbz: =>
milestone: NEEDS_TRIAGE => SSSD 1.7.0 owner: somebody => sgallagh
owner: sgallagh => jhrozek priority: minor => critical
summary: RFE: Ability to set a domain as case sensitive or insensitive => [RFE] Ability to set a domain as case sensitive or insensitive
status: new => assigned
patch: 0 => 1
Fixed by: - 4e9631a - c811965 - 940e033 - a26ea06 - 70a33bd - b3b42c4 - df5adba - 247a705
blockedby: => blocking: => resolution: => fixed status: assigned => closed
blocking: => 1104
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=735827 (Red Hat Enterprise Linux 6)
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=735827 735827]
Metadata Update from @gbarros: - Issue assigned to jhrozek - Issue marked as blocked by: #1104 - Issue set to the milestone: SSSD 1.7.0
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/1932
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Log in to comment on this ticket.