search for: krb5cc_11104

...lid starting Expires Service principal > 02/12/2024 08:39:44 02/12/2024 18:39:44 krbtgt/CAMPUS > renew until 02/13/2024 08:39:40 > > so this ticket is valid until 12. February 18:39. Fine. Not really, my tickets have a renewal time of one week i.e. klist -c /tmp/krb5cc_11104 Ticket cache: FILE:/tmp/krb5cc_11104 Default principal: rowland at SAMDOM.EXAMPLE.COM Valid starting Expires Service principal 12/02/24 07:56:02 12/02/24 17:56:02 krbtgt/SAMDOM.EXAMPLE.COM at SAMDOM.EXAMPLE.COM renew until 19/02/24 07:56:02 >And I can > refresh it using...

...Service principal > > 02/12/2024 08:39:44 02/12/2024 18:39:44 krbtgt/CAMPUS > > renew until 02/13/2024 08:39:40 > > > > so this ticket is valid until 12. February 18:39. Fine. > > Not really, my tickets have a renewal time of one week i.e. > > klist -c /tmp/krb5cc_11104 > Ticket cache: FILE:/tmp/krb5cc_11104 > Default principal: rowland at SAMDOM.EXAMPLE.COM > > Valid starting Expires Service principal > 12/02/24 07:56:02 12/02/24 17:56:02 krbtgt/ > SAMDOM.EXAMPLE.COM at SAMDOM.EXAMPLE.COM > renew until 19/02/24 07:56:...

Good day please excuse my delayed response. Thanks for the hint with the machine account. I will try this. I realised I can also manually refresh Kerberos tickets. I have the following: $ klist Valid starting Expires Service principal 02/12/2024 08:39:44 02/12/2024 18:39:44 krbtgt/CAMPUS renew until 02/13/2024 08:39:40 so this ticket is valid until 12. February 18:39.

...Service principal > > 02/12/2024 08:39:44 02/12/2024 18:39:44 krbtgt/CAMPUS > > renew until 02/13/2024 08:39:40 > > > > so this ticket is valid until 12. February 18:39. Fine. > > Not really, my tickets have a renewal time of one week i.e. > > klist -c /tmp/krb5cc_11104 > Ticket cache: FILE:/tmp/krb5cc_11104 > Default principal: rowland at SAMDOM.EXAMPLE.COM > > Valid starting Expires Service principal > 12/02/24 07:56:02 12/02/24 17:56:02 krbtgt/ > SAMDOM.EXAMPLE.COM at SAMDOM.EXAMPLE.COM > renew until 19/02/24 07:56:...