Full sudo refresh is scheduled even if there is no sudo responder #2500

sssd-bot · 2020-05-02T12:37:45Z

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/1458

Created at 2012-08-06 17:42:23 by jhrozek
Closed as Fixed
Assigned to pbrezina

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().

Comments

Comment from pbrezina at 2012-08-07 11:18:26

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().

Comment from dpal at 2012-08-09 16:01:44

Fields changed

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

Comment from pbrezina at 2012-08-23 12:56:40

Fields changed

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

Comment from pbrezina at 2012-09-05 15:06:11

Fields changed

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

Comment from pbrezina at 2012-09-05 16:43:32

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

resolution: fixed =>
status: closed => reopened