Bug 1201977

Summary: RFE: add more debugging to IPA LDAP group resolution
Product: Red Hat Enterprise Linux 7 Reporter: Paul Wayper <pwayper>
Component: sssdAssignee: SSSD Maintainers <sssd-maint>
Status: CLOSED DUPLICATE QA Contact: Kaushik Banerjee <kbanerje>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: grajaiya, jgalipea, jhrozek, lslebodn, mkosek, mzidek, pbrezina, preichl, pvoborni, rcritten
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-16 12:15:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paul Wayper 2015-03-14 07:10:49 UTC 
Description of problem:

If there is a problem in the parsing of a group in IPA using the get_ipa_groupname() function, there is no information about what caused the problem is returned or emitted in the debugging log.  There are eight distinct failure modes; four of them cause the group to be silently ignored, while the other four cause the failure of all group parsing.

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

How reproducible:

Always

1. Cause a replication failure, or any other problem that would cause ldb_dn_validate() to fail with an EINVAL.
2. Try to log in on a system with HBAC.

Actual results:

3. Service is denied.

Expected results:

3. Invalid records would be ignored, and any remaining rules that would allow users to be logged in are acted on.

Additional info:

I have a git commit that would emit more debugging information for the exit conditions in get_ipa_groupname().
Comment 2 Petr Vobornik 2015-03-16 11:38:14 UTC 
changing component to sssd - get_ipa_groupname() is an sssd function
Comment 3 Jakub Hrozek 2015-03-16 12:15:14 UTC 

*** This bug has been marked as a duplicate of bug 1202245 ***