#1458 Full sudo refresh is scheduled even if there is no sudo responder
Closed: Fixed None Opened 6 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

2 years ago

Login to comment on this ticket.

Metadata