#3112 When sssd.conf is missing, create one with id_provider=files
Closed: Fixed 4 years ago Opened 5 years ago by mzidek.

The sssctl tool generates sssd.conf when sssd.conf is missing. Is this expected or a bug?

Steps to reproduce:
1. delete or rename sssd.conf
2. run some sssctl command (for example sssctl user admin)
3. Following sssd.conf is created

[sssd]
config_file_version = 2
services = nss, pam
domains = shadowutils

[nss]

[pam]

[domain/shadowutils]
id_provider = proxy
proxy_lib_name = files

auth_provider = proxy
proxy_pam_target = sssd-shadowutils

proxy_fast_alias = True

As discussed on the phone yesterday, this is expected, but we should instead create a config with id_provider=files when it's avialable.

milestone: NEEDS_TRIAGE => SSSD 1.15 Beta
summary: sssctl creates sssd.conf when missing => When sssd.conf is missing, create one with id_provider=files

Fields changed

rhbz: => todo

Fields changed

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

Metadata Update from @mzidek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.15.3

4 years ago

Metadata Update from @lslebodn:
- Custom field component reset
- Custom field design_review reset
- Custom field mark reset
- Custom field patch adjusted to on (was: 1)
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Custom field type reset
- Custom field version reset
- Issue close_status updated to: None

4 years ago

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

4 years ago

Metadata Update from @lslebodn:
- Custom field design_review reset
- Custom field mark reset
- Custom field review reset
- Custom field sensitive reset
- Custom field testsupdated reset
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 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/4145

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