#1458 Full sudo refresh is scheduled even if there is no sudo responder
Closed: Fixed None Opened 10 years ago by jhrozek.

The "full" sudo refresh is currently always scheduled on back end startup, even though there is no sudo responder configured. This triggers an LDAP connection and a search right after the back end starts.

We should only schedule the refresh when we need it. One possible way might be on receiving sudo responder registration in client_registration().

If you want to disable specific module you can always set it to none in sssd.conf (sudo_provider = none). But if you insist on doing it in the code directly I would suggest that we initialize only those backend modules that have appropriate responder configured. Instead of initializing them in be_process_init() we would do it during client_registration().

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.0 RC2
rhbz: => 0

Fields changed

owner: somebody => pbrezina
proposed_priority: => Undefined
status: new => assigned

Fields changed

patch: 0 => 1
resolution: => fixed
status: assigned => closed

I have closed it by accident. The patch is on the list.

resolution: fixed =>
status: closed => reopened

master: 30f029e

resolution: => fixed
status: reopened => closed

Metadata Update from @jhrozek:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.9.0 RC1

5 years ago

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

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.

Login to comment on this ticket.