You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To support configuration changes at runtime, it must be possible to update and remove ranges. As a first step I would recommend that the changes will only affect new requests and not the cached data, because in general changes to centrally manages ranges should be done with care to avoid conflicts. In a later release we can decided if we just want to invalidate all cached entries of the domain which idrange was modified or if a smarter check is needed to invalidate only objects which are affected by the change.
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.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1981
To support configuration changes at runtime, it must be possible to update and remove ranges. As a first step I would recommend that the changes will only affect new requests and not the cached data, because in general changes to centrally manages ranges should be done with care to avoid conflicts. In a later release we can decided if we just want to invalidate all cached entries of the domain which idrange was modified or if a smarter check is needed to invalidate only objects which are affected by the change.
Comments
Comment from dpal at 2013-06-27 16:31:08
A sub ticket of the 1.11 feature.
rhbz: => 0
Comment from jhrozek at 2013-06-28 23:55:13
Moving open tickets from 1.11 beta to 1.11 beta2
milestone: SSSD 1.11 beta => SSSD 1.11 beta 2
Comment from jhrozek at 2013-07-24 15:04:16
Fields changed
milestone: SSSD 1.11 beta 2 => SSSD 1.11 beta 3
Comment from dpal at 2013-07-30 09:58:01
Fields changed
milestone: SSSD 1.11 beta 3 => Interim Bucket
priority: minor => major
Comment from dpal at 2013-07-30 12:54:43
Fields changed
milestone: Interim Bucket => SSSD 1.12 beta
Comment from dpal at 2013-12-02 21:36:27
Fields changed
milestone: SSSD 1.12 beta => SSSD 1.14 beta
Comment from jhrozek at 2016-02-16 13:38:18
Sumit agreed in IRC that this ticket is not in the 1.14 scope
mark: => 0
milestone: SSSD 1.14 beta => SSSD 1.15 beta
sensitive: => 0
Comment from sbose at 2017-02-24 15:02:44
Metadata Update from @sbose:
Comment from thalman at 2020-03-13 13:56:50
Metadata Update from @thalman:
Comment from pbrezina at 2020-03-24 14:11:46
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.
Comment from pbrezina at 2020-03-24 14:11:47
Metadata Update from @pbrezina:
The text was updated successfully, but these errors were encountered: