#3359 Allow to disable krb5 locator plugin selectively
Closed: Fixed 7 years ago Opened 7 years ago by sbose.

There are use-cases where it might be necessary to connect to a specific KDC, see e.g. https://bugzilla.redhat.com/show_bug.cgi?id=1072939.
Due to the way how a KDC is lookup up by libkrb5 it is not possible for a caller to bypass the results returned by a locator plugin. So even it the client uses an individual krb5 config file which lists the expected KDC the result of the locator plugin is still preferred.
To allow those use-cases it should be possible to disable SSSD's krb5 locator plugin for a specific client.


Metadata Update from @sbose:
- Issue assigned to sbose

7 years ago

Metadata Update from @sbose:
- Custom field patch adjusted to on

7 years ago

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to todo

7 years ago

Metadata Update from @jhrozek:
- Custom field rhbz adjusted to todo

7 years ago

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

7 years ago

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

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

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