Learn more about these different git repos.
Other Git URLs
When using GetUserGroups, also non-POSIX groups were returned. Using the new object interface, these groups are not being returned anymore. This difference is mentioned nowhere, so anyone switching to new interface can get confused easily.
Adding any information about this change to documentation (or a big warning about not supporting non-POSIX groups) would be helpful.
This could be added to Introspection message of the old function. I don't want to retroactively change the function behaviour, plus the new methods will support non-posix groups in some time.
Sorry I overlooked this ticket was filed into the 'void' milestone, moving back to NEEDS_TRIAGE for proper attention.
Metadata Update from @veruu: - Issue set to the milestone: void
It is still in void milestone. Moving to NEEDS_TRIAGE
Metadata Update from @lslebodn: - Custom field component reset - Custom field design_review reset - Custom field mark reset - Custom field patch reset - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset - Custom field type reset - Custom field version reset - Issue close_status updated to: None
Metadata Update from @lslebodn: - Custom field design_review reset - Custom field mark reset - Custom field patch reset - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset - Issue set to the milestone: NEEDS_TRIAGE (was: void)
Metadata Update from @lslebodn: - Custom field component adjusted to SSSD Wiki - Custom field design_review reset - Custom field mark reset - Custom field patch reset - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset - Custom field type adjusted to documentation - Custom field version adjusted to 1.13.1
when we implement the accountsservice API, we should also fix the documentation of the existing API
Metadata Update from @jhrozek: - Custom field design_review reset - Custom field mark reset - Custom field patch reset - Custom field review reset - Custom field sensitive reset - Custom field testsupdated reset - Issue set to the milestone: SSSD Future releases (no date set yet) (was: NEEDS_TRIAGE)
Metadata Update from @thalman: - Custom field design_review reset (from false) - Custom field mark reset (from false) - Custom field patch reset (from false) - Custom field review reset (from false) - Custom field sensitive reset (from false) - Custom field testsupdated reset (from false) - 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/3908
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.