Preauth hook and authusername hook are not used

I want to use ingo to manage my sieve filter through dovecot

Mon, 22 Aug 2011 11:21:00 +0000

I want to use ingo to manage my sieve filter through dovecot/managesieved. The problem is that i use logins without a domain part for horde. I want to use a preauth hook with ingo to append the domain to the username. In IMP it is working and i see my mails. In INGO the preauth hook is also executed but when i want to see the actual sieve script or save one to the server i get an "Authentication failed.". In the dovecot log i can see that the horde username is used without the domain appended. I also tried to use the authusername hook but it also does not work because it seems that it is not used (No log message is seen in the log). After digging into the code it looks like only the horde login is used in ingo/lib/Ingo.php, function getTransport().

As Jan mentioned on the list, this is the correct behavior.

Mon, 22 Aug 2011 17:55:37 +0000

As Jan mentioned on the list, this is the correct behavior. Ingo is currently written to only use Horde authentication values (e.g. Ingo_Application::_auth() is empty). Thus, there is no need to call auth alteration methods during initial authentication into Ingo. Two solutions for you: 1. Store this information in a separate variable. 2. Rewrite Ingo to use the application auth capability (e.g. similar to IMP), in which case these hooks become available.

I added the ability in Ingo to use the imp user data. The pa

Wed, 24 Aug 2011 00:25:44 +0000

I added the ability in Ingo to use the imp user data. The patch is attached. has only been quickly tested. Perhabs you guys can have a look at it. with regards Jonathan

> I added the ability in Ingo to use the imp user data. The

Wed, 24 Aug 2011 04:50:59 +0000

> I added the ability in Ingo to use the imp user data. The patch is > attached. has only been quickly tested. That will probably work locally. But that will not be added to Ingo since 1) it improperly accesses IMP directly and 2) is not the correct way to add authentication to an application. 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).

> Even if 1 and 2 weren't issues, it still won't be added to

Wed, 24 Aug 2011 11:25:10 +0000

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

>> Even if 1 and 2 weren't issues, it still won't be added t

Tue, 30 Aug 2011 19:22:08 +0000

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

> Appinitialized is called when an application is first init

Tue, 30 Aug 2011 21:22:08 +0000

> 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. I agree that it is a lot of overhead to add extra auth for Ingo. Just for my own knowledge: Is there a "horde" way to access the Imp auth data? Because for me it does make sense to couple the auth of Ingo to Imp as its settings are also under the Imp menu and sieve rules are set on the mail server. If i should ask this on the mailing list just say it. I am using this ticket only because it may be interesting for other people. Thanks for your help Jonathan

> Just for my own knowledge: Is there a "horde" way to acce

Tue, 30 Aug 2011 21:29:35 +0000

> Just for my own knowledge: Is there a "horde" way to access the Imp > auth data? Because for me it does make sense to couple the auth of > Ingo to Imp as its settings are also under the Imp menu and sieve > rules are set on the mail server. $ob = $GLOBALS['registry']->call('mail/imapOb'); $username = $ob->getParam('username');

Hello With the introduction of the Factory folder the pat

Wed, 05 Sep 2012 22:02:24 +0000

Hello With the introduction of the Factory folder the patch does not work anymore. When i want to get the imap object i have a infinit loop as imp is not initialized at this moment and the password is not already set Do you have any ideas how i can get the credentials from imp in ingo? With regards Jonathan

>> Just for my own knowledge: Is there a "horde" way to acc

Thu, 13 Dec 2012 16:46:24 +0000

>> Just for my own knowledge: Is there a "horde" way to access the Imp >> auth data? Because for me it does make sense to couple the auth of >> Ingo to Imp as its settings are also under the Imp menu and sieve >> rules are set on the mail server. > > $ob = $GLOBALS['registry']->call('mail/imapOb'); > $username = $ob->getParam('username'); Hi, I tried to use hooks to authenticate against dovecot managesieve in ingo 3.0.1 with no success. I'm using exactly same way how to get username and password from imap login, both values 'username' and 'password' are filled correctly, but I stil receiving: dovecot: managesieve-login: Disconnected (auth failed, 1 attempts): user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Thanks Petr this is my hooks.php class Ingo_Hooks { public function transport_auth($driver) { $ob = $GLOBALS['registry']->call('mail/imapOb'); return array( 'username' => $ob->getParam('username'), 'password' => $ob->getParam('password') ); } } What could be wrong? Thanks Petr

> this is my hooks.php > > class Ingo_Hooks > { > pu

Thu, 13 Dec 2012 22:59:28 +0000

> this is my hooks.php > > class Ingo_Hooks > { > public function transport_auth($driver) > { > $ob = $GLOBALS['registry']->call('mail/imapOb'); > return array( > 'username' => $ob->getParam('username'), > 'password' => $ob->getParam('password') > ); > > } > } Try to add: 'euser' => $ob->getParam('username') to the array. with regards Jonathan

>> this is my hooks.php >> >> class Ingo_Hooks >> { >>

Fri, 14 Dec 2012 22:00:34 +0000

>> this is my hooks.php >> >> class Ingo_Hooks >> { >> public function transport_auth($driver) >> { >> $ob = $GLOBALS['registry']->call('mail/imapOb'); >> return array( >> 'username' => $ob->getParam('username'), >> 'password' => $ob->getParam('password') >> ); >> >> } >> } > > Try to add: > > 'euser' => $ob->getParam('username') > > to the array. > > with regards > > Jonathan thank you Jonathan, next time I must read more carefully, euser for sieve is mentioned in this file Petr