#890 [RFE] Ability to set a domain as case sensitive or insensitive
Closed: Fixed None Opened 9 years ago by gbarros.

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]:

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.

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]:

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?

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: =>

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.7.0
owner: somebody => sgallagh

Fields changed

owner: sgallagh => jhrozek
priority: minor => critical

Fields changed

summary: RFE: Ability to set a domain as case sensitive or insensitive => [RFE] Ability to set a domain as case sensitive or insensitive

Fields changed

status: new => assigned

Fields changed

patch: 0 => 1

Fixed by:
- 4e9631a
- c811965
- 940e033
- a26ea06
- 70a33bd
- b3b42c4
- df5adba
- 247a705

blockedby: =>
blocking: =>
resolution: => fixed
status: assigned => closed

Fields changed

blocking: => 1104

Metadata Update from @gbarros:
- Issue assigned to jhrozek
- Issue marked as blocked by: #1104
- Issue set to the milestone: SSSD 1.7.0

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/1932

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