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

[bugs at horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/10448
------------------------------------------------------------------------------
  Ticket           | 10448
  Aktualisiert Von | joniw at t-online.de
  Zusammenfassung  | Preauth hook and authusername hook are not used
  Warteschlange    | Ingo
  Version          | Git master
  Typ              | Bug
  Status           | Not A Bug
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


joniw at t-online.de (2011-08-24 11:25) hat geschrieben:

> 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.

My problem is that i only need an email address for applications which  
use the mailserver (like imp and ingo at the moment). All other  
authentication is done against the ldap server. So if i rewrite the  
username in the horde hooks all applications use the mail address  
which is not what i want.

I also tried to implement the authentication for ingo but that is a  
really hard thing for me.