#2253 Check IPA idranges before saving them to the cache
Closed: Fixed Opened by sbose.

The IPA backend currently only checks the idranges on startup when reading them from the cache. If there are idranges with conflicts stored on the server the IPA backend will just put them into the cache without checking them which might lead to issues when SSSD is restarted and the idranges are checked.

Before saving the data from the server to the cache the idranges should be checked for collisions that same way as it is done during startup.


Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1067361

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=1067361 1067361]

Fields changed

priority: major => critical

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.11.5

  • master:
    • 096a9678919fae460342469989b97fd47d812823
    • f69f3581658351003a6d9245045e41d0efb85022
    • ff6e24f4474cca6226cd44c47ba2ec6ba6cf9a16
  • sssd-1-11:
    • c9160931bd57b66bb1bf8312c05b9cb6da2497bc
    • 751a77c04f15e059dcca07f8fd72702db90fb83e
    • b71e463bb8dca5aaca8e9677a92b679390c7b966

resolution: => fixed
status: new => closed

Metadata Update from @sbose:
- Issue assigned to sbose
- Issue set to the milestone: SSSD 1.11.5

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

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.

Metadata