Learn more about these different git repos.
Other Git URLs
This is a follow up to issue #1507. Currently the sdap_id_op code has several issues (such as touching the online/offline status directly). I don't think each LDAP search issues from the back ends should need to deal with the sdap_id_op requests and retries, but there should be a wrapper around those which evaluates the error codes.
We also need to get rid of the ignore_mark_offline flag, instead the id_op should return an error and let the wrapper deal with it, usually by setting the domain offline or inactive.
The idea is to put all the _retry logic into one request. Given the connection is cached, I believe it can be put into ldap_search where you either connect or reuse the connection if available and try to reconnect if it fails.
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.0
Metadata Update from @jhrozek: - Issue priority set to: major
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.1 (was: SSSD 2.0)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)
Metadata Update from @thalman: - Issue tagged with: Future milestone
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/4656
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.
Metadata Update from @pbrezina: - Issue close_status updated to: cloned-to-github - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.