Bug 870316 - groups are not resolved correctly
Summary: groups are not resolved correctly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: nss-pam-ldapd
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-26 07:15 UTC by Marcus Moeller
Modified: 2013-05-06 12:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-06 12:34:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Marcus Moeller 2012-10-26 07:15:17 UTC
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 09:52:57 UTC
I agree it might be the time to move to the 0.8 version in Fedora.

Comment 2 Arthur de Jong 2012-10-26 13:21:50 UTC
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 13:29:23 UTC
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.