[Tickets #11297] Re: Fatal authentication error not catched

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/11297
------------------------------------------------------------------------------
  Ticket             | 11297
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Fatal authentication error not catched
  Queue              | IMP
  Version            | Git develop
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          | 6
  Patch              |
-Owners             |
+Owners             | Michael Slusarz, Jan Schneider
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2012-10-06 14:54) wrote:

>> I would like to know *why* the authentication is failing (you already
>> logged into IMP, right?), but this should fix the authentication
>> exception.
>
> *Why* doesn't matter, I enforced this by shutting down the IMAP  
> server. The point is that we need to gracefully handle if something  
> happens on the server side.

My mistake.  I was worried that the issue was something like the  
cached IMAP session object becoming invalid.  I wasn't aware that this  
issue was caused by known downtime in the IMAP server.

> Regular pages continue to work fine now even if IMAP authentication  
> in IMP fails. But inside IMP, this is still not correctly handled.  
> AJAX requests get an empty response, i.e. the user is not logged out  
> of IMP.

Is authentication actually failing on the IMAP server?  Or is the IMAP  
server not reachable on the network?  The latter will NOT cause a  
logout (since it is not an authentication error - once authenticated,  
it is assumed the user remains authenticated until the server  
explicitly indicates authentication is wrong).