[SSSD-users] Not getting any ticket in ccache in CentOS 6.6

Jakub Hrozek jhrozek at redhat.com
Wed Apr 15 06:51:47 UTC 2015


On Wed, Apr 15, 2015 at 08:21:08AM +0200, Lukas Slebodnik wrote:
> On (14/04/15 23:36), Ola Nystrom wrote:
> >Removed the line from krb5.conf
> >restarted sssd
> >
> >Still same issue
> >
> >[ola at galaxy ~]$ klist
> >klist: No credentials cache found while retrieving principal name
> >[ola at galaxy ~]$ kinit
> >Password for ola at ENSKEDE.LOCAL:
> >[ola at galaxy ~]$ klist
> >Ticket cache: KEYRING:persistent:11103
> >Default principal: ola at ENSKEDE.LOCAL
> >
> >Valid starting     Expires            Service principal
> >04/14/15 23:36:33  04/15/15 09:36:36  krbtgt/ENSKEDE.LOCAL at ENSKEDE.LOCAL
> >        renew until 04/21/15 23:36:33
> >[ola at galaxy ~]$ cat /etc/krb5.conf
> >[logging]
> > default = FILE:/var/log/krb5libs.log
> > kdc = FILE:/var/log/krb5kdc.log
> > admin_server = FILE:/var/log/kadmind.log
> >
> >[libdefaults]
> > default_realm = ENSKEDE.LOCAL
> > dns_lookup_realm = true
> > dns_lookup_kdc = true
> > ticket_lifetime = 24h
> > renew_lifetime = 7d
> > forwardable = true
> > rdns = false
> >[ola at galaxy ~]$
> >
> 
> Please try to find out in sssd log file whether ccache was created (FILE).
> You should see full patch in log file to this ccache file. If the file with
> ticket exists and is a valid (test with exporting KRB5CCNAME) then
> we need to figure out why the enviroment variable KRB5CCNAME was not set after
> logging in

cache should be cleared, otherwise the KEYRING ccname might be reused..


More information about the sssd-users mailing list