sssd crashes in offline mode(when system is NOT connected to network) if AD forest is defined in ad_access_filter

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3083

• Created at 2016-07-07 13:55:12 by jhrozek
• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1353174

---

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

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

Description of problem:
sssd crashes in offline mode(when system is NOT connected to network) if AD
forest is defined in  ad_access_filter

Version-Release number of selected component (if applicable):
sssd-1.13.0-40.el7_2.4
sssd-common-1.13.0-40.el7_2.4

How reproducible:
Always when ad_access_filter is having FOREST defined.

Steps to Reproduce:
1. In sssd.conf define filter as shown below:
---
ad_access_filter=FOREST:EXAMPLE.COM:(&(|(memberOf=CN=GR_LINUX_USER,OU=Groups,DC
=example,DC=com)(memberOf=CN=GR_ADMIN_LINUX,OU=Groups,DC=example,DC=com)))
---

2. Then try to login as AD user when system is NOT connected to network.

3. sssd will crash.

Actual results:
sssd crashes and abrt dumps a core if system is NOT connected to network:
---
[abrt] sssd-common-1.13.0-40.el7_2.4: sssd_be killed by SIGSEGV
---

Expected results:
AD users should be able to login and sssd shouldn't crash

Additional info:
Following filer instead works perfect:
---
ad_access_filter=(&(|(memberOf=CN=GR_LINUX_USER,OU=Groups,DC=example,DC=com)(me
mberOf=CN=GR_ADMIN_LINUX,OU=Groups,DC=example,DC=com)))
---

Comments

---

Comment from jhrozek at 2016-07-14 17:35:54

Fields changed

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

---

Comment from jhrozek at 2017-02-24 14:29:41

Metadata Update from @jhrozek:

• Issue set to the milestone: SSSD Future releases (no date set yet)

---

Comment from thalman at 2020-03-13 11:37:10

Metadata Update from @thalman:

• Custom field design_review reset (from 0)
• Custom field mark reset (from 0)
• Custom field patch reset (from 0)
• Custom field review reset (from 0)
• Custom field sensitive reset (from 0)
• Custom field testsupdated reset (from 0)
• Issue close_status updated to: None
• Issue tagged with: Future milestone

[andreboscatto]

Dear Contributor/User,

Recognizing the importance of addressing enhancements, bugs, and issues for the SSSD project's quality and reliability, we also need to consider our long-term goals and resource constraints.

After thoughtful consideration, regrettably, we are unable to address this request at this time. To avoid any misconception, we're closing it; however, we encourage continued collaboration and contributions from anyone interested.

We apologize for any inconvenience and appreciate your understanding of our resource limitations. While you're welcome to open a new issue (or reopen this one), immediate attention may not be guaranteed due to competing priorities.

Thank you once again for sharing your feedback. We look forward to ongoing collaboration to deliver the best possible solutions, supporting in any way we can.

Best regards,
André Boscatto

CC: @tscherf