search for: krb5cc_12345_zb1ylu

...ound no definite solution. I tried to specify 'cruid=%(USERID)' in the case of pam_mount, or 'cruid=12345' in the manual case (12345 being the literal uid of the user). I also tried getting rid of the strange file ending of the krb5 key cache, because in my case it is e.g. "krb5cc_12345_Zb1yLU". And I tried chowning the file to root:root instead of user:domain users. Nothing worked. The krb5 key cache files are created in /tmp on user logon. Is this the correct lookup directory, in the first place? Kerberos as such is working correctly. Domain logons work, kinit as well. This i...

...ution. I tried to specify > 'cruid=%(USERID)' in the case of pam_mount, or 'cruid=12345' in the > manual case (12345 being the literal uid of the user). I also tried > getting rid of the strange file ending of the krb5 key cache, because > in my case it is e.g. "krb5cc_12345_Zb1yLU". And I tried chowning the > file to root:root instead of user:domain users. Nothing worked. > > The krb5 key cache files are created in /tmp on user logon. Is this > the correct lookup directory, in the first place? > > Kerberos as such is working correctly. Domain logons...

...o specify >> 'cruid=%(USERID)' in the case of pam_mount, or 'cruid=12345' in the >> manual case (12345 being the literal uid of the user). I also tried >> getting rid of the strange file ending of the krb5 key cache, because >> in my case it is e.g. "krb5cc_12345_Zb1yLU". And I tried chowning the >> file to root:root instead of user:domain users. Nothing worked. >> >> The krb5 key cache files are created in /tmp on user logon. Is this >> the correct lookup directory, in the first place? >> >> Kerberos as such is working c...