#2460 service lookups returned in lowercase with case_sensitive=preserving
Closed: Fixed None Opened 6 years ago by jhrozek.

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

Description of problem:
service lookups returned in lowercase with case_sensitive=preserving

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
dn: cn=Svc1,ou=Services,dc=example,dc=com
objectClass: ipService
cn: svc1_alias1
cn: SVC1_Alias2
cn: Svc1
ipServicePort: 65535
ipServiceProtocol: Tcp
ipServiceProtocol: udp
ipServiceProtocol: dummy_proto

2. Configure and start sssd with case_sensitive=preserving

3. Lookup service

Actual results:
# getent services Svc1
svc1                  65535/tcp svc1_alias1 svc1_alias2

# getent services 65535/TCP
svc1                  65535/tcp svc1_alias1 svc1_alias2

Expected results:
Case should not be lowered

Additional info:

Reassigning to Michal. Please note this has a lower priority than the non-root sssd feature.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
owner: somebody => mzidek
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.3

This upstream ticket was requesting by a downstream. Bumping the priority to make sure the ticket is closed as soon as possible.

priority: major => critical

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.3

4 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/3502

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.