[Tickets #9733] Re: Password lost during hordeauth authentication via API

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/9733
------------------------------------------------------------------------------
  Ticket             | 9733
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Password lost during hordeauth authentication via API
  Queue              | Horde Base
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 3. High
  Milestone          | 4.0.1
  Patch              |
  Owners             | Horde Developers
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2011-04-14 17:31) wrote:

>> A separate issue thuough is why the new mail notifications are even
>> chcecked when calling code that would never be able to do anything
>> with them. Seems like a waste of resources to me.
>
> The logic on whether to display is fully contained within the new  
> mail notification decorator, however.  Not sure how else this could  
> work.

But there is no display context when we are talking about non-horde  
client requests for rpc.php

> Disabling notifications altogether for the AS request might be an  
> option.  But on the flip side, ignoring all notifications might not  
> be a good idea either since when you push a notification on the  
> stack in the code, you have an expectation that it will eventually  
> be processed somehow.

There is no mechanism in place to display any notifications for AS  
requests, or for some other rpc requests for that matter, so disabling  
notifications in these cases makes sense to me