Learn more about these different git repos.
Other Git URLs
In case the 'domains' option is not specifed, the SSSD should be able to just read all the domain sections and use them. This enhancement would reduce the configuration required to start SSSD.
See also ticket #1165
Fields changed
description: In case the 'domains' option is not specifed, the SSSD should be able to just read all the domain sections and use them. This enhancement would reduce the configuration required to start SSSD.
See also => In case the 'domains' option is not specifed, the SSSD should be able to just read all the domain sections and use them. This enhancement would reduce the configuration required to start SSSD.
milestone: NEEDS_TRIAGE => SSSD 1.13 beta
rhbz: => 0
mark: => 1
Makes total sense for supporting the local back end.
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
Would be great when we implement the local users support to simplify configuration, but not required right now.
milestone: SSSD 1.14 beta => SSSD 1.15 beta sensitive: => 0
Metadata Update from @jhrozek: - Issue set to the milestone: SSSD Future releases (no date set yet)
Metadata Update from @jhrozek: - Custom field design_review reset (from 0) - Custom field mark adjusted to on (was: 1) - Custom field patch reset (from 0) - Custom field review reset (from 0) - Custom field sensitive reset (from 0) - Custom field testsupdated reset (from 0) - Issue close_status updated to: None - Issue set to the milestone: SSSD 2.0 (was: SSSD Future releases (no date set yet))
Metadata Update from @jhrozek: - Custom field design_review 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 set to the milestone: SSSD 2.1 (was: SSSD 2.0)
Metadata Update from @jhrozek: - Custom field design_review 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 set to the milestone: SSSD 2.2 (was: SSSD 2.1)
Metadata Update from @jhrozek: - Custom field design_review 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 set to the milestone: SSSD 2.3 (was: SSSD 2.2)
Duplicit to https://pagure.io/SSSD/sssd/issue/3735
Metadata Update from @thalman: - Custom field design_review 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 @thalman: - Custom field design_review adjusted to on (was: false) - Custom field patch adjusted to on (was: false) - Custom field review adjusted to on (was: false) - Custom field sensitive adjusted to on (was: false) - Custom field testsupdated adjusted to on (was: false) - Issue close_status updated to: duplicate - 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/3272
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.