Learn more about these different git repos.
Other Git URLs
It would be nice if krb5_renew_interval could be set with a delimiter in the same manner as krb5_renewable_lifetime and krb5_lifetime. For example, using 4h in addition to 14400.
It is also worth noting that currently with debug_level = 3 sssd doesn't complain anything if one specifies krb5_renew_interval = 4h. However, system-config-authentication will fail to start in that case.
milestone: NEEDS_TRIAGE => SSSD 1.7.0
milestone: SSSD 1.8.0 => SSSD 1.9.0
milestone: SSSD 1.9.0 => SSSD Kerberos improvements
rhbz: => 0
proposed_priority: => Important
rhbz: 0 => todo
summary: Allow setting krb5_renew_interval with a delimiter => [RFE] Allow setting krb5_renew_interval with a delimiter
Moving all the features planned for 1.10 release into 1.10 beta.
milestone: SSSD Kerberos Improvements Feature => SSSD 1.10 beta
priority: minor => major
selected: => Not need
Moving tickets that are not a priority for SSSD 1.10 into the next release.
milestone: SSSD 1.10 beta => SSSD 1.11 beta
design_review: => 0
owner: somebody => arielb
status: new => assigned
Ariel contributed a patch which was acked upstream. Moving to 1.10 beta.
milestone: SSSD 1.11 beta => SSSD 1.10 beta
patch: 0 => 1
review: => 0
resolution: => fixed
status: assigned => closed
changelog: => krb5_renew_interval can be set with a delimiter in the same manner as krb5_renewable_lifetime and krb5_lifetime. For example, using 4h in addition to 14400.
design: => N/A (trivial)
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1030486
rhbz: todo => [https://bugzilla.redhat.com/show_bug.cgi?id=1030486 1030486]
Metadata Update from @myllynen:
- Issue assigned to arielb
- Issue set to the milestone: SSSD 1.10 beta
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:
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.
to comment on this ticket.