Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1324107

Summary: GPO: Access denied after blocking connection to AD.
Product: Red Hat Enterprise Linux 6 Reporter: Dan Lavu <dlavu>
Component: sssdAssignee: SSSD Maintainers <sssd-maint>
Status: CLOSED ERRATA QA Contact: Steeve Goveas <sgoveas>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.8CC: grajaiya, jhrozek, lslebodn, mkosek, mzidek, nsoman, pbrezina
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: sssd-1.13.3-30.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-21 09:55:22 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: 1365846    

Description Dan Lavu 2016-04-05 14:14:55 UTC 
Description of problem:
When SSSD goes offline due to a network connectivity issue, the first login atempt fails and does not allow the user to login or su. Following attempts do work.

Upstream ticket: https://fedorahosted.org/sssd/ticket/2964

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


How reproducible:
Always.


Steps to Reproduce:
1. Setup SSSD and permit user to access host via GPO access.
2. Force SSSD to go offline using iptables and block the port. 

iptables -F

iptables -A INPUT -s $AD_SERVER1_IP -j DROP
iptables -A OUTPUT -d $AD_SERVER1_IP -j DROP

3. Attempt to login or su

** Or run downstrean QE tests ** 

Actual results:
User is not allowed to login.

Expected results:
User can login.


Additional info:
Comment 6 Jakub Hrozek 2016-04-05 19:59:40 UTC 
Upstream ticket:
https://fedorahosted.org/sssd/ticket/2964
Comment 8 Lukas Slebodnik 2016-04-12 13:17:54 UTC 
master:
* bdd533146cb2da71b7c39ad0efa2e5baca7257eb

sssd-1-13:
* 33973418462b75592122343e318045a6905c475b
Comment 11 Dan Lavu 2017-01-12 00:59:04 UTC 
Verified against sssd-client.x86_64 0:1.13.3-53.el6


::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: ad_gpo_007: ad gpo offline mode
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   PASS   ] :: File '/var/log/sssd/sssd_sssdad.com.log' should contain 'offline' 
:: [  BEGIN   ] :: Running 'su_success 'allow_u-1666474' Secret123'
spawn su --shell /bin/sh nobody -- -c su --shell /bin/true -- "$1" -- allow_u-1666474
Password: :: [   PASS   ] :: Command 'su_success 'allow_u-1666474' Secret123' (Expected 0, got 0)
:: [  BEGIN   ] :: Running 'su_success 'allow_gu-1666474' Secret123'
spawn su --shell /bin/sh nobody -- -c su --shell /bin/true -- "$1" -- allow_gu-1666474
Password: :: [   PASS   ] :: Command 'su_success 'allow_gu-1666474' Secret123' (Expected 0, got 0)
:: [  BEGIN   ] :: Running 'su_fail 'regular_u-1666474' Secret123'
spawn su --shell /bin/sh nobody -- -c su --shell /bin/true -- "$1" -- regular_u-1666474
Password:
Comment 13 errata-xmlrpc 2017-03-21 09:55:22 UTC 
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.

https://rhn.redhat.com/errata/RHBA-2017-0632.html