Yes we have some thoughts about it. But it is not something that we will do soon. 1.6 is baked, 1.7 is also has a different focus but 1.8 or 2.0 would be aligned with the server side changes that will make looking into this more attractive. Putting into 2.0 bucket for now.

Would be very useful if you provide more detailed use cases and work flows and examples of the configuration you want to see.

For example: user has credential of type X, machine is online (or offline), SSSD is configured to do Y, user does Z, and SSSD performs <something>.

milestone: NEEDS_TRIAGE => SSSD 2.0

Fields changed

rhbz: => 0

Fields changed

blockedby: =>
blocking: =>
feature_milestone: =>
proposed_priority: => Optional

This ticket has been evaluated for inclusion into SSSD 1.10 release and was decided to be excluded since it does not match the main goals and themes of the release. It might be considered for later releases.

moving the ticket to needs_triage for discussion.

changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
mark: => 0
milestone: SSSD 2.0 => NEEDS_TRIAGE
review: => 0
selected: =>
sensitive: => 0

We will split the failover per-domain (now it's per-back end), but not per provider.

resolution: => wontfix
status: new => closed

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

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.