#1121 request for Heimdal support
Closed: Fixed None Opened 8 years ago by rambaldi.


Would it be possible to extend SSSD and also support Heimdal as Kerberos
client implementation?

My setup is as follows:

  • server with

    • Heimdal KDC
    • openldap
    • pam_ldap / nss_ldap
  • laptops/workstations with

    • mit kerberos clients
    • SSSD

I would like to use SSSD on all my machines, but because SSSD does not
support Heimdal I cannot replace pam_ldap/nss_ldap on the server.


Fields changed

component: SSSD => Kerberos Provider
owner: somebody => sgallagh
patch: 0 => 1
priority: major => minor
status: new => assigned

It is not something that is in our plans at the moment.
If there is an external contribution to do this and there is someone who would agree to maintain it, then we will consider.
Otherwise you would be better off moving to FreeIPA in Fedora or IdM in RHEL 6.2 (same thing) on the server side. It is free and has more than you currently have on the server, easier to use and being actively enhanced to be more feature rich.

milestone: NEEDS_TRIAGE => SSSD Deferred

Putting back in NEEDS_TRIAGE, we already have a patch, if confirmed working we can put the feature in 1.8.0 as experimental.

milestone: SSSD Deferred => NEEDS_TRIAGE

Patch appears to be working based on feedback from the original reporter.

Our plan will be to include this patch in the 1.7.0 release, pending formal code-review later today.

milestone: NEEDS_TRIAGE => SSSD 1.7.0
version: 1.6.3 => master

Fixed (experimentally) in
- 7685916 (master)
- cbe8cbd (sssd-1-7)

resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

Metadata Update from @rambaldi:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.7.0

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

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.