Learn more about these different git repos.
Other Git URLs
This came up during a discussion I had with Simo the other day about ghost users and group memberships mechanisms in general.
Currently we use an ASQ call during sysdb_initgroups() to retrieve all groups the user is a member of by dereferencing his memberof attribute. But since we introduced the ghost attribute we might use a filter on the ghost attribute such as (&(objectclass=group)(ghost=username)) and eventually even reconsider if we need the memberof attribute at all.
(&(objectclass=group)(ghost=username))
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.11 beta rhbz: => todo summary: Reconsider the use of memberof in initgroups => [RFE] Reconsider the use of memberof in initgroups type: defect => enhancement
milestone: SSSD 1.11 beta => SSSD 1.12 beta
changelog: => milestone: SSSD 1.14 beta => SSSD 1.13 beta review: => 0 selected: =>
mark: => 0
This is a good tracker on whether we need the memberof plugin at all or whether we can drastically reduce it.
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
Mass-moving tickets not planned for the 1.13 release to 1.14
milestone: SSSD 1.13 backlog => SSSD 1.14 beta
This ticket makes sense, but the 1.14 milestone is already too big. I'm moving the ticket to 1.15 beta
milestone: SSSD 1.14 beta => SSSD 1.15 beta sensitive: => 0
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @thalman: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue tagged with: Canditate to close
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)
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/2695
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.