#1500 SSSD's default ccache location needs to be updated (again), and the man pages should reflect it
Closed: Fixed None Opened 10 years ago by jhrozek.

https://bugzilla.redhat.com/show_bug.cgi?id=851304 (Fedora)

Description of problem:
For the sake of packages which follow the advice currently given at
https://fedoraproject.org/wiki/Features/KRB5CacheMove, SSSD should switch from
creating DIR:/run/user/${UID}/ccdir to creating DIR:/run/user/${UID}/krb5cc.
The sssd-krb5(5) man page should also reflect the defaults that we're putting
in place.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Log in using pam_sss for authentication.
2. Use "klist" to check where your credentials have been stored.
3. Check if nfs-utils (see bug #833024 for patch and discussion) and cifs-utils
(bug #848223) can find your credentials.

Actual results:
Both are currently being asked to switch (or have switched) to effectively
globbing using "krb5cc*" to find FILE: and DIR: ccaches where they previously
used "krb5cc_*" as a glob for FILE: ccaches, so a ccache named "ccdir" isn't
going to be found.

Expected results:
Both cifs.upcall and rpc.gssd can find the ccache that SSSD creates.

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
milestone: NEEDS_TRIAGE => SSSD 1.9.0 beta 7
owner: somebody => jhrozek
patch: 0 => 1
status: new => assigned
tests: => 0
testsupdated: => 0
upgrade: => 0

Fixed in master: d60a79f

resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.9.0 beta 7

5 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/2542

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.