Please review the restriction on this ticket because it does not need any privacy, nobody can take any advantage out of this bug.

cc'ing asanka@ for more insights on the bug.

Please let me know if I can help with anything regarding this bug, is easy to replicate and I think that this ticket could also cover the case where a kerberos ticket did not exist or was expired the moment Chrome was started.

If the ticket appeared later Chrome will fail to pick it up, requiring you to restart the browser.

I think that Chrome should refresh the list of kerberos tickets from time to time (like 5 minutes), avoiding a restart. Another alternative would be to remember when you refreshed the list of tokens and if when doing the SPNEGO handshake to attempt to refresh the list if last check was n-minutes ago.

Is there any command I can execute to force Chrome to refresh without having to restart it?

You are renewing the ticket after it expires? I'm guessing, you mean you obtain new tickets using the credentials in your keychain? Once the tickets expire, they can't be renewed.

Could you specify how you are testing Kerberos login?

Also, does 'klist -l' show more than one credentials cache?

Apologies for the delay in getting to this.

[sorin.sbarnea] Archiving bug due to lack of response to comment #7.  If you're still having the issue, please post back with the requested information within a couple days, and I'll reopen it.