#2461 Proxy Provider: Fails to lookup case sensitive users and groups with case_sensitive=preserving
Closed: Fixed None Opened 5 years ago by jhrozek.

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

Description of problem:
Fails to lookup users and groups with case_sensitive=preserving in proxy
provider

Version-Release number of selected component (if applicable):
sssd-1.12.1-3.el7

How reproducible:
Always

Steps to Reproduce:
1. Add the following ldif to ldap server
dn: uid=User_CS1,ou=Users,dc=example,dc=com
objectClass: posixAccount
objectClass: account
cn: User_CS1
homeDirectory: /home/User_CS1
uid: User_CS1_Alias
uid: User_CS1
uidNumber: 304560
gidNumber: 304560

2. Configure sssd as proxy backend and add case_sensitive=preserving in the
domain section:
[domain/PROXY]
debug_level=0xFFF0
id_provider = proxy
proxy_lib_name = ldap
proxy_pam_target = sssdproxyldap
case_sensitive = preserving

3. Lookup an user

Actual results:
Lookup fails to return anything.
# getent -s sss passwd User_CS1
#

Domain log shows:
(Thu Oct 16 14:44:57 2014) [sssd[be[PROXY]]] [be_get_account_info] (0x0200):
Got request for [4097][1][name=user_cs1]
(Thu Oct 16 14:44:57 2014) [sssd[be[PROXY]]] [get_pw_name] (0x0400): Searching
user by name (user_cs1)
(Thu Oct 16 14:44:57 2014) [sssd[be[PROXY]]] [handle_getpw_result] (0x0080):
User not found.
(Thu Oct 16 14:44:57 2014) [sssd[be[PROXY]]] [delete_user] (0x0400): User
user_cs1 does not exist (or is invalid) on remote server, deleting!


But, looking up directly from nss_ldap shows:
# getent -s ldap passwd User_CS1
User_CS1:*:304560:304560:User_CS1:/home/User_CS1:

Expected results:


Additional info:

Fields changed

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: no => 0
milestone: NEEDS_TRIAGE => SSSD 1.12.3
review: True => 0
selected: =>
testsupdated: => 0

Fields changed

owner: somebody => mzidek

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

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

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