[Tickets #10448] Re: Preauth hook and authusername hook are not used

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/10448
------------------------------------------------------------------------------
  Ticket             | 10448
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Preauth hook and authusername hook are not used
  Queue              | Ingo
  Version            | Git master
  Type               | Bug
  State              | Not A Bug
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-08-30 19:22) wrote:

>> Even if 1 and 2 weren't issues, it still won't be added to Ingo since
>> Ingo does not need full authentication.  Your particular use case is
>> a fringe case, and I am not convinced that it couldn't be handled a
>> different way (e.g. using the appinitialized hook).
>
> Ok i get your point. As far as i understood it, ingo always uses the  
> horde login and does not save an own login. So how can the  
> appinitialized hook help me? If there is a "horde" way to do it i  
> would use it.

Appinitialized is called when an application is first initialized.  In  
that app, you could do something like storing the value you want to  
use in ingo in a session variable.  You will still have to alter other  
code in ingo to use this value, however.

The issue for you is that you are trying to use ingo in a non-standard  
way.  The correct way to fix would be to add authentication to Ingo.   
But this is not-insignificant overhead, and I personally don't see the  
advantage to adding this feature (at the expense of performance) when  
its usage would be extremely limited.