Bug 870316 - groups are not resolved correctly
groups are not resolved correctly
Product: Fedora
Classification: Fedora
Component: nss-pam-ldapd (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Nalin Dahyabhai
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-10-26 03:15 EDT by Marcus Moeller
Modified: 2013-05-06 08:34 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-05-06 08:34:34 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marcus Moeller 2012-10-26 03:15:17 EDT
Description of problem:
Fedora does not ship the latest nslcd Version available. It contains a build of the 0.7.x tree with backports.

With this version, only primary groups are resolved in our setup.

I have created a test build of the latest 0.8.11 release which works correctly.

I would prefer if you could always provide the latest stable version in Fedora, even if oldstable is needed for EL.

Otherwise, please pick the related patches and include it in your build.

If you need some help, in maintaining a more current version for Fedora, feel free to ask.

Version-Release number of selected component (if applicable):
Version    : 0.7.16
Release    : 4.fc18
Comment 1 Jakub Hrozek 2012-10-26 05:52:57 EDT
I agree it might be the time to move to the 0.8 version in Fedora.
Comment 2 Arthur de Jong 2012-10-26 09:21:50 EDT
Just to avoid any confusion: release 0.8.11 of nss-pam-ldapd load's the secondary groups of the nslcd user when starting the nslcd daemon. It shouldn't change anything regarding secondary groups of LDAP users.
Comment 3 Marcus Moeller 2012-10-26 09:29:23 EDT
Dear Arthur. Thanks for your comment. I have not yet debugged what causes the problem on the version shipped with Fedora, I just made sure that it works with the latest release.

Note You need to log in before you can comment on or make changes to this bug.