Bug 1377213

Summary: ding-libs don't parse lines without an equal sign
Product: Red Hat Enterprise Linux 6 Reporter: Jakub Hrozek <jhrozek>
Component: ding-libsAssignee: Jakub Hrozek <jhrozek>
Status: CLOSED CURRENTRELEASE QA Contact: Steeve Goveas <sgoveas>
Severity: high Docs Contact:
Priority: high    
Version: 6.8CC: cww, dlavu, enewland, mkosek, mzidek, tscherf
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ding-libs-0.4.0-12.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1379325 1379582 (view as bug list) Environment:
Last Closed: 2017-06-05 16:11:56 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:
Bug Depends On:    
Bug Blocks: 1374813, 1379325, 1379582    

Description Jakub Hrozek 2016-09-19 08:39:23 UTC
Description of problem:
This bugzilla tracks the upstream ticket https://fedorahosted.org/sssd/ticket/2751

It's required to fix to process some GPO files from Windows.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jakub Hrozek 2016-09-19 09:23:21 UTC
Upstream ticket:
https://fedorahosted.org/sssd/ticket/2751

Comment 2 Jakub Hrozek 2016-09-21 14:42:16 UTC
Michal, can you add some steps to reproduce?

Comment 3 Michal Zidek 2016-09-21 15:07:42 UTC
Steps to reproduce:

1. configure SSSD as AD client with enforced GPO access control. Add this line to the domain section in sssd.conf

ad_gpo_access_control = enforcing

2. Create user1 in AD

3. create a GPO for access control on the AD server. The GPO must apply to the client machine and allow login for user1. The GPO ini file must contain line with no equal sign. For example add this as the last line in the GPO ini file

foo,"2"

4. try to login as user1 from AD

Current result:
Access for user1 is denied.

Expected result:
user1 should be able to login.