--On Friday, September 01, 2006 12:55 AM -0400 Sam Hartman via RT 
<rt-comment@krbdev.mit.edu> wrote:

> I strongly suspect that the context is ending when it expires and that
> SASL needs to do a better job of catching this error and reporting a
> connection problem.


Just to be clear, the problem happens when the ticket cache is refreshed. 
I.e., the tickets for the existing SASL/GSSAPI connection hadn't actually 
yet expired, just the ticket cache was refreshed with new tickets.  I can 
understand why the SASL/GSSAPI context would be closed out on *expiration* 
but I think a refresh shouldn't have this effect. ;)


--Quanah


--
Quanah Gibson-Mount
Principal Software Developer
ITS/Shared Application Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html