#998 Add a Kerberos provider option to set krb5_get_init_creds_opt_set_address_list
Closed: Invalid None Opened 12 years ago by jhrozek.

This option would be analogous to kinit's -a: request tickets with the local address(es).

Nalin said:
The krb5_get_init_creds_opt_set_address_list option is less important now that we default to using addressless tickets, but it probably won't hurt.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.8.0
priority: major => minor

Fields changed

type: defect => enhancement

Fields changed

blockedby: =>
blocking: =>
milestone: SSSD 1.8.0 => SSSD 1.9.0

Fields changed

milestone: SSSD 1.9.0 => SSSD Kerberos improvements

Fields changed

rhbz: => 0

Fields changed

feature_milestone: =>
proposed_priority: => Nice to have

Fields changed

proposed_priority: Nice to have => Undefined

I've spent some more time thinking about this. While I initially was in favor of it, I can't come up with any scenarios where I'd want to explicitly set SSSD's behavior to be different from the rest of the system, which heeds the default value for this setting (extra_addresses/noaddresses), as set (or not) in /etc/krb5.conf. It's less work for the administrator to just have to change it once, in /etc/krb5.conf, so I'm going to mark this as won't-fix.

_comment0: I've spent some more time thinking about this. While it's an easy knob to provide, and I initially was in favor of it, I can't come up with any scenarios where I'd want to explicitly set SSSD's behavior to be ''different'' from the rest of the system, which heeds the default value for this setting (''extra_addresses''/''noaddresses''), as set (or not) in /etc/krb5.conf. It's less work for the administrator to just have to change it once, in /etc/krb5.conf, so I'm going to mark this as won't-fix. => 1345156414197930
cc: => nalin
resolution: => wontfix
status: new => closed

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD Kerberos Improvements Feature

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

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