Learn more about these different git repos.
Other Git URLs
k5login_directory If set, the library will look for a local user’s k5login file within the named directory, with a filename corresponding to the local username. If not set, the library will look for k5login files in the user’s home directory, with the filename .k5login.
As of now we assume that the .k5login always exists in user's home directory.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.7.0 priority: major => minor
milestone: SSSD 1.8.0 => SSSD 1.9.0 patch: => 0
blockedby: => blocking: => milestone: SSSD 1.9.0 => SSSD Kerberos improvements rhbz: =>
rhbz: => 0
feature_milestone: => proposed_priority: => Nice to have
Moving all the features planned for 1.10 release into 1.10 beta.
milestone: SSSD Kerberos Improvements Feature => SSSD 1.10 beta
design: => design_review: => 0 fedora_test_page: => summary: [enh] support k5login_directory feature. => [RFE] support k5login_directory feature. type: defect => enhancement
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
mark: => 0
changelog: => milestone: SSSD 1.13 beta => SSSD 1.13 backlog priority: minor => trivial review: => 0
Mass-moving tickets not planned for any immediate release and re-setting priority.
milestone: SSSD 1.13 backlog => SSSD Deferred priority: trivial => major
I think this is better solved with the localauth plugin, so I would close this ticket.
review: 0 => 1 sensitive: => 0
resolution: => wontfix status: new => closed
Metadata Update from @gowrishankar: - Issue set to the milestone: SSSD Patches welcome
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/1873
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.