Bug 804065 - Service lookup using case-sensitive protocol names doesn't work when case_sensitive=false.
Service lookup using case-sensitive protocol names doesn't work when case_sen...
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Stephen Gallagher
Depends On:
  Show dependency treegraph
Reported: 2012-03-16 09:05 EDT by Kaushik Banerjee
Modified: 2012-06-20 07:56 EDT (History)
4 users (show)

See Also:
Fixed In Version: sssd-1.8.0-20.el6
Doc Type: Bug Fix
Doc Text:
No documentation needed
Story Points: ---
Clone Of:
Last Closed: 2012-06-20 07:56:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Kaushik Banerjee 2012-03-16 09:05:10 EDT
Description of problem:
Unable to lookup services using case-sensitive protocol names.

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

How reproducible:

Steps to Reproduce:
1. Add the following service in ldap server:
dn: cn=Svc4,ou=Services,dc=example,dc=com
objectClass: ipService
cn: svc4_alias1
cn: SVC4_Alias2
ipServicePort: 12345
ipServiceProtocol: Tcp
ipServiceProtocol: udp

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
Actual results:
Service lookup using case-sensitive protocol names doesn't work.

Expected results:
Service lookup using case-sensitive protocol names should work.

Additional info:
Comment 2 Jakub Hrozek 2012-03-17 17:52:42 EDT
Upstream ticket:
Comment 3 Jakub Hrozek 2012-03-17 18:05:54 EDT
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.
Comment 4 Stephen Gallagher 2012-03-20 11:26:18 EDT
Upstream ticket:
Comment 7 Kaushik Banerjee 2012-04-02 16:19:00 EDT
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
Comment 8 Jakub Hrozek 2012-04-03 14:45:49 EDT
    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.
    New Contents:
No documentation needed
Comment 10 errata-xmlrpc 2012-06-20 07:56:10 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.