Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 202135 - add support for nsRoles objects in nss_ldap
add support for nsRoles objects in nss_ldap
Product: Fedora
Classification: Fedora
Component: nss_ldap (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 2006-08-10 18:13 EDT by Subhendu Ghosh
Modified: 2016-10-04 00:28 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-17 18:08:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
PADL Software 382 None None None Never

  None (edit)
Description Subhendu Ghosh 2006-08-10 18:13:43 EDT
Support for querying nsRole attributes (in Fedora DS) via pam_ldap/nss_ldap
Comment 1 Matthew Miller 2007-04-06 13:19:53 EDT
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.

[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
Comment 2 Bug Zapper 2008-04-03 23:30:37 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 3 Nalin Dahyabhai 2008-04-07 11:06:08 EDT
Well, I know it hasn't been implemented yet.

Subhendu, can you elaborate on what exactly the modules are supposed to be doing
with these attributes?
Comment 4 Bug Zapper 2008-05-13 22:16:44 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Comment 5 Guil Barros 2008-11-17 11:18:36 EST
I have the same need. It would be beneficial if nss_ldap were able to restrict user access based on nsRole. This would be similar to the current pam_groupdn option in ldap.conf but much more flexible.
Comment 6 Nalin Dahyabhai 2008-11-17 18:08:20 EST
nss_ldap doesn't have much use for nsRole -- the filters used for looking up entries are already customizable, not that I'd recommend doing that.

Submitting a patch to add an additional access check to pam_ldap, using the "pam_nsrole" configuration setting as a means of specifying a role that the user's entry must have, and closing the bug report here.

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