#2229 Ship an immutable recovery mode config for local accounts
Closed: wontfix 3 years ago by pbrezina. Opened 10 years ago by jhrozek.

When SSSD manages local users, it should also ship an immutable configuration file that would be used in cases when the administrator's config doesn't work well or is not provided at all.

When implementing and testing this feature, we should make sure that the basic functionality works with this config. At least authentication and password changes must be supported.


Fields changed

blocking: => 2228
keywords: => localaccounts

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13 beta

Fields changed

rhbz: => todo

Fields changed

mark: => 1

This will be important for local accounts handling, but it's out of scope for 1.13

milestone: SSSD 1.13 beta => SSSD 1.13 backlog

Mass-moving tickets not planned for the 1.13 release to 1.14

milestone: SSSD 1.13 backlog => SSSD 1.14 beta

Fields changed

cc: => mzidek@redhat.com
sensitive: => 0

When we work on this, the immutable config should also detail why there is no more elaborate config (ie we don't know what the remote domain is)

The local users support won't be added in 1.14. We will need the fallback config for the secrets responder, which is tracked separately in #1552, but the providers work is not scoped for 1.14.

milestone: SSSD 1.14 beta => SSSD 1.15 beta

Fields changed

owner: somebody => jhrozek
patch: 0 => 1
status: new => assigned

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue marked as blocked by: #2228
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

master:

This ticket is fixed partially because if the config cannot be loaded, we still fail
the patches only handle the 'no config' part, not the 'config is broken part'

This ticket is fixed partially because if the config cannot be loaded, we still fail
the patches only handle the 'no config' part, not the 'config is broken part'

Metadata Update from @jhrozek:
- Assignee reset

4 years ago

Metadata Update from @thalman:
- Custom field blocking reset (from 2228)
- Custom field design_review reset (from 0)
- Custom field mark adjusted to on (was: 1)
- Custom field patch adjusted to on (was: 1)
- Custom field review reset (from 0)
- Custom field sensitive reset (from 0)
- Custom field testsupdated reset (from 0)
- Issue tagged with: Canditate to close

4 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

3 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/3271

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