Red Hat Bugzilla – Bug 804065
Service lookup using case-sensitive protocol names doesn't work when case_sensitive=false.
Last modified: 2012-06-20 07:56:10 EDT
Description of problem:
Unable to lookup services using case-sensitive protocol names.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add the following service in ldap server:
2. sssd.conf domain section is configured as:
id_provider = ldap
ldap_uri = ldap://ldapserver.example.com
ldap_search_base = dc=example,dc=com
case_sensitive = false
3. Lookup service by service name and udp protocol:
# getent -s sss services svc4
svc4 12345/tcp svc4_alias1 svc4_alias2 svc4_alias2 svc4
# getent -s sss services 12345/udp
svc4 12345/udp svc4_alias1 svc4_alias2 svc4_alias2 svc4
4. Lookup service by service name and "Tcp" protocol:
# getent -s sss services 12345/tcp <=== Doesn't return anything
# getent -s sss services 12345/Tcp <=== Doesn't return anything
Service lookup using case-sensitive protocol names doesn't work.
Service lookup using case-sensitive protocol names should work.
Looking up a service by port including the protocol was broken because of the same bug upstream ticket #1259 is tracking, so I just linked this bugzilla to that upstream ticket.
However, if the domain is case-insensitive, we don't support looking up by port and case-insensitive protocol because we only store the original protocol name, no aliases.
I've opened https://fedorahosted.org/sssd/ticket/1260 to track the case-insensitive issue.
Verified in version:
# rpm -qi sssd | head
Name : sssd Relocations: (not relocatable)
Version : 1.8.0 Vendor: Red Hat, Inc.
Release : 20.el6 Build Date: Fri 30 Mar 2012 06:45:57 PM IST
Install Date: Mon 02 Apr 2012 05:36:37 PM IST Build Host: x86-002.build.bos.redhat.com
Group : Applications/System Source RPM: sssd-1.8.0-20.el6.src.rpm
Size : 7865577 License: GPLv3+
Signature : (none)
Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL : http://fedorahosted.org/sssd/
Summary : System Security Services Daemon
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
No documentation needed
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.