Learn more about these different git repos.
Other Git URLs
LDAP server-side timeouts are currently not handled in SSSD. It might make sense to talk to LDAP server developers to see if it would help to set the option as well.
Especially in cases where SSSD might trigger a long running operation on the server but drops the request after a few seconds on the client. The server is then still busy preparing the response for the client and when it is ready it is not needed any more.
Since this bug was already there for some time, I don't think it's urgent to fix soon.
Thierry thinks it would be a good idea, we can fix this in master
Fields changed
owner: somebody => preichl
rhbz: => 0
milestone: NEEDS_TRIAGE => SSSD 1.14 alpha
This makes sense as part of the general refactoring of the LDAP provider
milestone: SSSD 1.14 alpha => SSSD 1.14 beta
The LDAP refactoring will happen in the next version.
milestone: SSSD 1.14 beta => SSSD 1.15 beta
Metadata Update from @preichl: - Issue assigned to preichl - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @thalman: - Custom field design_review reset (from 0) - Custom field mark reset (from 0) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - 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/3884
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.