SSSD / sssd

#3304 Only build the local provider conditionally
Closed: Fixed Opened by pbrezina.

Closed: Fixed
Reopen Issue

We have refactored data provider API and almost finished conversion of responders to cache_req code. I think this gives us a good chance to finally create a dummy local provider process to get rid of all special cases in responders.

It would simplify future maintenance and helps us avoid local provider issues since it is not really used in real environment we tend to often forget about it.

Creating such provider is trivial.

When the files provider is merged, don't we want to just remove the local provider?

That would be even better. I thought you don't want to go this way.

As discussed yesterday, the current plan is to deprecate the local provider first and remove it eventually if nobody complains.

So the current scope of this ticket is to add a configure-time flag that would be disabled by default and must be enabled for the local provider to be built.

milestone: NEEDS_TRIAGE => SSSD 1.15.1
summary: create dummy local provider => Only build the local provider conditionally

Metadata Update from @pbrezina:
- Issue set to the milestone: SSSD 1.15.1

Since we are releasing 1.15.1 today, I'm moving all unfinished tickets from 1.15.1 to 1.15.2

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue close_status updated to: None

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue set to the milestone: SSSD 1.15.2 (was: SSSD 1.15.1)

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue set to the milestone: SSSD 1.15.3 (was: SSSD 1.15.2)

Metadata Update from @jhrozek:
- Custom field design_review reset
- Custom field mark reset
- Custom field patch reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue set to the milestone: SSSD 1.15.4 (was: SSSD 1.15.3)

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue tagged with: cleanup-two-point-oh

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue untagged with: cleanup-two-point-oh
- Issue set to the milestone: SSSD 2.0 (was: SSSD 1.15.4)

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue tagged with: breaks compatibility

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue priority set to: blocker (was: major)

Metadata Update from @fidencio:
- Issue assigned to fidencio

Metadata Update from @fidencio:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue tagged with: PR
  • master:
    0e211b8ba30c3adcdeef21ca1339b194cbfffb04
    82d51b7feba8df49df3f7a023d2b16aba26a858e
    b8946c46e04e8b5329e4d95f9a67b4a76f883bb2
    c075e2865b2fbedb6a7eeb6a90780c6dbffeb5fd
    15342ebe8c22738e947728f06c6833b5be09eca8
    5a87af9128c5468ce1f2e55602c9d3ec05987b8d
    a24f0c202ed7ea159ad04eb19b506b7f21ad41cc
    2e8fe6a3dd022721e1ff476c8fd7af317a535d63
    728e4be10fc7a7b3173b74b1f597e835914c9abf
    99b5bb54447287da5031dcd2bfebeef8b47d52d7
    a8a9e66a852ba8aa1371e2e1897d49f3feee76da
    064ca0b46eed06977dbd32c2bd894f71dc43be2e
    6ebcc59b9458c5a118cd182c07a840fa6756a43e
    35a200d5bd84d6a6742e77ffda9945e37134d721
    2243b348976705ca81da954cb1ead1f406d01918
    7d483737f3763947a5b8a43efbfaf31f54f956a4

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)

Metadata Update from @jhrozek:
- Custom field design_review reset (from false)
- Custom field mark reset (from false)
- Custom field patch reset (from false)
- Custom field review reset (from false)
- Custom field sensitive reset (from false)
- Custom field testsupdated reset (from false)
- Issue close_status updated to: Fixed
- 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/4337

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.
Metadata

PR breaks compatibility

None
None
Lowest
defect
SSSD
1.15.0
false
false
false
false
false
false
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.