[ingo] WG: Using IMP Auth in Ingo

[Michael M Slusarz]

Quoting Jonathan Westerholt <joniw at t-online.de>:

> Hello
>
> Forgot to CC to the list
>
> Jonathan
>
>> -----Ursprüngliche Nachricht-----
>> Von: Jonathan Westerholt [mailto:joniw at t-online.de]
>> Gesendet: Donnerstag, 27. September 2012 19:50
>> An: 'Michael M Slusarz'
>> Betreff: AW: [ingo] Using IMP Auth in Ingo
>>
>> Hello Michael
>>
>> With xdebug disabled i get after a short waiting time:
>>
>> PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried
>> to allocate 523800 bytes) in
>> /opt/webpages/horde/git/framework/Core/lib/Horde/Registry.php on line
>> 33
>>
>> The problem seems to be that imp initializes ingo which in turn tries to
> access
>> the imap object which leads to a new init of imp. So we have an endless
> loop
>> here.

Well sure: this is expected in bootstrapping code.  Your ingo code has  
to check if IMP is authenticated to first; if not, you can't grab the  
username/password or else there will be an infinite circular loop.

In other words, your authentication code CANNOT rely on grabbing  
authentication details from a backend that may not yet be initialized.  
  That's just a limitation of authentication/initialization procedures.

michael

___________________________________
Michael Slusarz [slusarz at horde.org]