#2449 Enable the sssd krb5 localauth plugin by default
Closed: Fixed None Opened 8 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Fedora): Bug 1145788

When krb5 gains the ability to have include directories, we should prepare a snippet to drop into that directory and enable the localauth plugin. This is a packaging task only.


Downstream needs this, moving to 1.12.

blockedby: =>
blocking: =>
changelog: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
mark: => 0
milestone: NEEDS_TRIAGE => SSSD 1.12.2
review: True => 0
selected: =>
testsupdated: => 0

We need to do a release as requested by downstream. Moving tickets that are not fixed already or very close to acking to 1.12.3

milestone: SSSD 1.12.2 => SSSD 1.12.3

Kerberos doesn't have the required functionality in time. In the short term, we will implement ticket #2473 and this one will be implemented in a later release. So far moving to 1.13, the next one.

milestone: SSSD 1.12.3 => SSSD 1.13 beta

We should implement this when Kerberos provides the required functionality.

milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: major => critical

Fields changed

priority: critical => major

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

milestone: SSSD 1.13 backlog => SSSD 1.14 beta

The functionality was just included in krb5, we should take advantage of it!

priority: major => critical
sensitive: => 0

Fields changed

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

Since there is a patch available, moving to 1.14 alpha.

milestone: SSSD 1.14 beta => SSSD 1.14 alpha

Fields changed

patch: 1 => 0

We need to do an Alpha release today, so I'm moving this ticket out of the Alpha milestone.

milestone: SSSD 1.14 alpha => SSSD 1.14.0

The plugin has been enabled for a long time now.

resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to lslebodn
- Issue set to the milestone: SSSD 1.14.0

5 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/3491

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