Learn more about these different git repos.
Other Git URLs
Simo had this idea on IRC the other day. Instead of always performing all optimizations regardless of the request type, we should investigate letting the responder choose what optimization should be performed. The idea is that identity look ups would be able to optimize more aggresively, even using the modifyTimestamp and authentication lookups, like initgroups during PAM conversation would choose slower, but more precise path, like only comparing the attributes.
The reason is that some LDAP servers can let the admin modify some attributes, but not change the modifyTimestamp value, which means we never detect the attribute value change.
Implementation-wise, we should probably look into extending the sysdb transaction with some flags, like SYSDB_OPTIMIZE_MODSTAMP, SYSDB_OPTIMIZE_ATTRVALS and SYSDB_OPTIMIZE_NONE.
We might want to revert the commit 00f3c5c after fixing this bug.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.14.2 priority: major => critical
rhbz: => todo
I think this would be a nice goal of refactoring before the work on 1.15 features starts.
milestone: SSSD 1.14.2 => NEEDS_TRIAGE
This is an ideal task for 1.15 refactoring.
milestone: NEEDS_TRIAGE => SSSD 1.15 Alpha
milestone: SSSD 1.15.0 => SSSD 1.15 Beta
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 1.15.3
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 close_status updated to: None - Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)
Metadata Update from @jhrozek: - 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: cleanup-one-sixteen
Metadata Update from @jhrozek: - 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 untagged with: cleanup-one-sixteen - Issue priority set to: minor (was: critical) - Issue set to the milestone: SSSD 1.16.0 (was: SSSD 1.15.4)
Since we are required to release a new upstream tarball no later than Friday Oct-20, I'm moving tickets that will not be closed by that date to the next milestone, 1.16.1
Metadata Update from @jhrozek: - 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 set to the milestone: SSSD 1.16.1 (was: SSSD 1.16.0)
Metadata Update from @jhrozek: - 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: postpone-to-future-releases
Metadata Update from @jhrozek: - 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 untagged with: postpone-to-future-releases - Issue set to the milestone: SSSD Future releases (no date set yet) (was: SSSD 1.16.1)
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/4159
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.