This problem is fixed by commit f834f712548db811695ea0fd6d6b31d3bd03e2a3 (master), which was created as a solution of ticket #2361.

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

Fields changed

owner: somebody => lslebodn

Fields changed

summary: supplemental group resolution fails with sssd 1.11.6-30.el6 => supplemental group resolution fails with sssd 1.11.6-30.el6 with id_provider=ldap connected to AD

We just need to push f834f712548db811695ea0fd6d6b31d3bd03e2a3 into sssd-1-11

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11.8

• sssd-1-11: 29e5b5d17d9700022958bf1f59bb861cdf68bb57

resolution: => fixed
status: new => closed

Apologies if this is the wrong place, but even after the latest sssd release on RHEL6 (sssd-1.11.6-30.el6_6.3.x86_64) I'm still getting intermittent problems with users having no supplemental groups. I have a case open with Red Hat Support, but I'm not getting very far, partly because it's so intermittent.

Is there anything else I can do to get this investigated further? Where is the right place to discuss this?

Replying to [comment:7 jberanek]:

Apologies if this is the wrong place, but even after the latest sssd release on RHEL6 (sssd-1.11.6-30.el6_6.3.x86_64) I'm still getting intermittent problems with users having no supplemental groups. I have a case open with Red Hat Support, but I'm not getting very far, partly because it's so intermittent.

I'm sorry to hear that. The patch from this ticket was reverted in upstream because it caused regressions with dereferencing attributes from OpenLDAP server.

Is there anything else I can do to get this investigated further? Where is the right place to discuss this?

But there is another patch in rhel6.6 which shoudl fix this problem as well #2483 (it fixes problem with Active Directory and ldap provider)

You can get faster response from upstream if you send mail to sssd-users mailing list.

Fields changed

cc: => john@redux.org.uk

Replying to [comment:6 jhrozek]:

• master: f834f712548db811695ea0fd6d6b31d3bd03e2a3
• sssd-1-11: 29e5b5d17d9700022958bf1f59bb861cdf68bb57

Previous patches were reverted by:

• master: 30c964ac455a9c26cdc391e849505b4312f733ae
• sssd-1-11: c6a7cf7be85539ea0460d9f07182b8b666efe412

Fields changed

resolution: fixed =>
status: closed => reopened

The comment 10 says that patches were reverted,
but bug was fixed in different ticket #2483.

Therefore changing state from closed:fixed to closed:duplicate

resolution: => duplicate
status: reopened => closed

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

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.