#1223 RFE: Provide group information in sssd query tool
Closed: wontfix 2 years ago by pbrezina. Opened 10 years ago by myllynen.

Related to ticket #1220, from https://fedorahosted.org/pipermail/sssd-devel/2012-February/008719.html:

  1. Group membership - how was group membership computed (in ldap we can have nested groups, not all groups have Unix attributes defined)

when possible.

Fields changed

milestone: NEEDS_TRIAGE => User/Group Info Tool Feature

Fields changed

rhbz: => 0

FYI the link describing this has been changed: https://lists.fedorahosted.org/pipermail/sssd-devel/2012-February/008719.html

design: =>
design_review: => 0
fedora_test_page: =>
selected: =>

Metadata Update from @myllynen:
- Issue set to the milestone: User/Group Info Tool Feature

5 years ago

Metadata Update from @jhrozek:
- Custom field design_review reset (from 0)
- Custom field patch reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue close_status updated to: None
- Issue set to the milestone: SSSD Patches welcome (was: User/Group Info Tool Feature)

3 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

2 years ago

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

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.

Login to comment on this ticket.