Ticket #128 (new enhancement)

Opened 5 years ago

Last modified 14 months ago

Enhancement request: Dynamic Groups

Reported by: mkosek Owned by:
Priority: major Milestone: FUTURE
Component: Directory Server Version:
Keywords: Cc: andrey.ivanov@…, dimitri.ars@…
Blocked By: Blocking:
Review: Needs Review Ticket origin: Community
Red Hat Bugzilla: 293821



From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR
1.1.4322; InfoPath.1)

Description of problem:
Would like to request a dynamic group functionality, similar to the dynamic
group overlay functionality in OpenLDAP:


Version-Release number of selected component (if applicable):

How reproducible:
Couldn't Reproduce

Steps to Reproduce:
N/A - enhancement request

Actual Results:

Expected Results:
A method for creating dynamic groups where the entry returned has the group
membership dynamically generated and returned as part of a list of dn's (i.e.
fill in the uniquemember values) based on an LDAP URI (similar to groupofURLs,
but have the server run the query instead of the client, and return the matches
as part of the uniquemember attr - openldap actually offers more flexibility
than this, but even supporting just ldap groups like this would be useful

Additional info:
This is an enhancement request, not a bug.

Change History

comment:1 Changed 5 years ago by rmeggins

  • Type changed from defect to enhancement

comment:2 Changed 5 years ago by rmeggins

  • Milestone changed from NEEDS_TRIAGE to FUTURE

batch update moving tickets to future

comment:3 Changed 5 years ago by rmeggins

  • Owner rmeggins deleted

comment:4 Changed 4 years ago by pj101

  • Cc andrey.ivanov@… added

comment:5 Changed 4 years ago by rmeggins

  • Ticket origin set to Community

set default ticket origin to Community

comment:6 Changed 4 years ago by nkinder

  • screened set to 1

Added initial screened field value.

comment:7 Changed 4 years ago by dimitriars

  • Cc dimitri.ars@… added

comment:8 Changed 14 months ago by nhosoi

  • Milestone changed from FUTURE to 0.0 NEEDS_TRIAGE

Is this still needed? need investigation? or low pri?

comment:9 Changed 14 months ago by nkinder

  • Milestone changed from 0.0 NEEDS_TRIAGE to FUTURE
Note: See TracTickets for help on using tickets.