#1512 [sssd[krb5_child[PID]]]: Credential cache directory /run/user/UID/ccdir does not exist
Closed: Fixed None Opened 7 years ago by dpal.

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

Description of problem:
sudo is failing in Fedora 18 (development) with identities via LDAP and
authorization via Kerberos.

Version-Release number of selected component (if applicable):
# rpm -qa | egrep 'krb5|systemd|sssd'

How reproducible:

Actual results:
User POV:
sudo date
[sudo] password for my_user_name:
Sorry, try again.
[sudo] password for my_user_name:
sudo: 1 incorrect password attempt

Log POV:
==> /var/log/messages <==
Aug 31 13:39:29 test-host [sssd[krb5_child[10593]]]: Credential cache directory
/run/user/my_uid/ccdir does not exist

==> /var/log/secure <==
Aug 31 13:39:29 test-host sudo: pam_sss(sudo:auth): system info: [Credential
cache directory /run/user/my_uid/ccdir does not exist]

No AVCs reported.

See attachment.

Fields changed

blockedby: =>
blocking: =>
coverity: =>
feature_milestone: =>
milestone: NEEDS_TRIAGE => SSSD 1.9.1
tests: => 0
testsupdated: => 0
upgrade: => 0

Fields changed

milestone: SSSD 1.9.1 => SSSD 1.9.2

Fields changed

owner: somebody => pbrezina
status: new => assigned

Neither me, nor Pavel nor the reporter can reproduce the issue anymore. Closing and worksforme. We will reopen the ticket if the bug strikes again.

resolution: => worksforme
status: assigned => closed

Fields changed

design: =>
design_review: => 0
fedora_test_page: =>
milestone: SSSD 1.9.2 => SSSD 1.9.4
resolution: worksforme =>
selected: =>
status: closed => reopened

We won't block the 1.9.4 release but deliver the fix to Fedora as a patch.

milestone: SSSD 1.9.4 => SSSD 1.9.5

I just wanted to add that if there is any patch you'd like tested, please do let me know as this is blocking my F18 deployment. I can easily build my own packages, so feel free to just toss a patch.

I apologize for the delay. I had to finish some pending RHEL tasks. I'll make sure there's a patch by COB Monday..

Fields changed

status: reopened => new

I managed to reproduce this issue and I will have patch ready tonight or tomorrow morning.

Fields changed

cc: => tibbs

Fields changed

patch: 0 => 1
status: new => assigned

resolution: => fixed
status: assigned => closed

Metadata Update from @dpal:
- Issue assigned to pbrezina
- Issue set to the milestone: SSSD 1.9.5

2 years ago

Login to comment on this ticket.