#38 provider configuration for LOCAL domain
Closed: Fixed None Opened 14 years ago by jhrozek.

With the current code in monitor.c, all providers are checked for the presence of "provider = " directive in the corresponding domain configuration. But there is no provider for LOCAL which results in some problems:

During startup, add_new_provider() fails and the LOCAL domain is not added to the list of active providers. This also manifests as the "[sssd] [add_new_provider] (0): Could not get provider configuration for [LOCAL]" error message.

During update of configuration, the LOCAL domain is found in the config file, but not in the old config, which makes the update_monitor_config function fail with "Service entry missing data".

The plan is probably to add a backend for LOCAL, or, at least in the meantime, special-case LOCAL domain.


After discussion with Simo, there is no reason to build a backend for LOCAL. We will instead treat LOCAL as a special case and ensure that it is properly included into the service list.

Assigning this bug to myself.

owner: somebody => sgallagh
status: new => assigned

Fixed in [d6b65c3]

milestone: SSSD 1.0 =>
resolution: => fixed
status: assigned => closed
version: 0.3.3 => 0.4

Fields changed

rhbz: => 0

Metadata Update from @jhrozek:
- Issue assigned to sgallagh

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

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.

Metadata