Summary | [passwd] imp is not activated. |
Queue | Passwd |
Queue Version | Git develop |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | Horde Developers (at) , ralf.lang (at) ralf-lang (dot) de |
Requester | aba (at) sundown (dot) cz |
Created | 11/27/2012 (4607 days ago) |
Due | |
Updated | 03/12/2013 (4502 days ago) |
Assigned | 12/03/2012 (4601 days ago) |
Resolved | 03/12/2013 (4502 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
commit da458cde92a2bddaff217cd1124ae3243a038b6e
Author: Michael M Slusarz <slusarz@horde.org>
Date: Tue Mar 12 17:07:37 2013 -0600
Add better logout message (
Bug #11766)passwd/lib/Basic.php | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
http://git.horde.org/horde-git/-/commit/da458cde92a2bddaff217cd1124ae3243a038b6e
State ⇒ Resolved
destroy the Horde session if the password change would affect anything
within the session. This is because, even with registry calls, there
can be no guarantee that, for example, an admin hasn't cached
something relating to the old password in a hook.
Our backend is not optimized to handle this kind of invasive session
change. Nor should it. This is an acceptable solution (and the
solution the vast majority of applications use).
commit 43f9253c42bfe053a64f3dc8386048626936e367
Author: Michael M Slusarz <slusarz@horde.org>
Date: Tue Mar 12 16:53:41 2013 -0600
[mms] Add option to destroy Horde session after changing password
(
Bug #11766).passwd/config/backends.php | 7 ++++---
passwd/docs/CHANGES | 1 +
passwd/docs/UPGRADING | 15 +++++++++++++++
passwd/lib/Basic.php | 9 ++++-----
passwd/package.xml | 1 +
5 files changed, 25 insertions(+), 8 deletions(-)
http://git.horde.org/horde-git/-/commit/43f9253c42bfe053a64f3dc8386048626936e367
6.0.4 and passwd 5.0-git.
Are there any suggestion on how to workaround this problem for us mere
mortals so we could use passwd to change passwords on IMAP servers and
have Imp handling Horde auth at the same time? As far as I could see
from git logs the patch which was aimed at fixing this problem had
been reverted after some discussion on the dev mailing list. So,
what's to do then?
Thanks in advance for updates on the topic.
thank you
Petr
thank you
Petr
commit f1a9c26a2e5e8b5edf4216f6278426593e4dda69
Author: Ralf Lang <lang@b1-systems.de>
Date: Mon Dec 3 16:32:19 2012 +0200
validate imap object's internal password against imp's auth
credentials in authenticateCallback.
This affects the root cause of
#11766,#11789,#10228imp/lib/Auth.php | 7 +++++++
1 files changed, 7 insertions(+), 0 deletions(-)
http://git.horde.org/horde-git/-/commit/f1a9c26a2e5e8b5edf4216f6278426593e4dda69
configuration of these both instances but I didn't found anything
interesting. I have no idea what could be wrong. Do you think that
could be done with imap server? On both sites is dovecot, maybe
different version. I can compare configuration, but question is-
isn't it too low to seek the problem there?
Any IMP action for authenticated session, even ->authenticate or
->transparent, implies PushApp and thus ->authenticated which in turn
triggers IMP_Auth->authenticationCallback.
That one however tries to build a whole IMP environment and reuses the
existing ->ob (IMP_Imap) instance to detect the namespace. This is
where it fails because of the old, unchanged credentials.
I'm preparing a patch but it looks rather ugly so far and I am not
sure it doesn't imply performance loss.
you are right that problem still persists.
Strange is, that on two horde webmail instances passwd has different
behaviour. On first it works now (and honestly i'm not sure if I test
it there when I opened this bug) and on second it still fails.
I compared horde "packages", versions, horde, imp, passwd
configuration of these both instances but I didn't found anything
interesting. I have no idea what could be wrong. Do you think that
could be done with imap server? On both sites is dovecot, maybe
different version. I can compare configuration, but question is- isn't
it too low to seek the problem there?
Petr
State ⇒ Assigned
What basically happens is this:
When Horde uses imp as authentication and password is changed by
passwd, for example via postfix admin database table, it also resets
the session. It does not (and cannot easily) reset the internally
stored imap connection.
I'm still resolving what happens afterwards.
I tried to add explicit re-authentication to passwd and additional
code to IMP_Auth which would destroy/reopen an imap connection if
parameter credentials do not match the IMAP ->ob credentials.
It does not get there though.
Somewhere in the stack between Horde's Auth_Application instance and
imp's auth_application instance (_base) it already tries to access the
imap object (probably part of application startup for an already
authenticated scenario) before it can run IMP_Auth->authenticate. I'm
still tracing where this happens, but any suggestions are welcome.
about imp or the imap components caching credentials and not
allowing to refresh them during a session. But I do not find that
ticket now, maybe it's resolved.
Assigned to Ralf Lang
Assigned to
about imp or the imap components caching credentials and not allowing
to refresh them during a session. But I do not find that ticket now,
maybe it's resolved.
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ Passwd
Summary ⇒ [passwd] imp is not activated.
Type ⇒ Bug
with the latest passwd I'm using postfixadmin (SQL) backend. Passwd
let me to change passwd but after submision I got this message to log
"2012 Nov 27 15:36:43 mail [passwd] imp is not activated. [pid 23717
on line 1457 of "/usr/share/php/Horde/Registry.php"]"
and following text on screen:
A fatal error has occurred
imp is not activated.
1. Horde_Notification_Handler->push() /var/www/webmail/passwd/index.php:146
2. Horde_Core_Notification_Handler_Decorator_Base->push()
/usr/share/php/Horde/Notification/Handler.php:255
3. Horde_Registry->pushApp()
/usr/share/php/Horde/Core/Notification/Handler/Decorator/Base.php:37
Details
The full error message is logged in Horde's log file, and is shown
below only to administrators. Non-administrative users will not see
error details.
Horde_Exception_PushApp Object
(
[application] => imp
[details] =>
[logged] => 1
[_logLevel:protected] => 0
[message:protected] => imp is not activated.
[string:Exception:private] =>
[code:protected] => 2
[file:protected] => /usr/share/php/Horde/Registry.php
[line:protected] => 1457
[trace:Exception:private] => Array
(
[0] => Array
(
[file] =>
/usr/share/php/Horde/Core/Notification/Handler/Decorator/Base.php
[line] => 37
[function] => pushApp
[class] => Horde_Registry
[type] => ->
[args] => Array
(
[0] => imp
[1] => Array
(
[check_perms] => 1
[logintasks] =>
)
)
)
[1] => Array
(
[file] => /usr/share/php/Horde/Notification/Handler.php
[line] => 255
[function] => push
[class] => Horde_Core_Notification_Handler_Decorator_Base
[type] => ->
[args] => Array
(
[0] => Horde_Core_Notification_Event_Status Object
(
[charset] => UTF-8
[message] => Failure in changing
password for Postfix Admin server: Authentication failed.
[flags] => Array
(
)
[type] => horde.error
)
[1] => Array
(
)
)
)
[2] => Array
(
[file] => /var/www/webmail/passwd/index.php
[line] => 146
[function] => push
[class] => Horde_Notification_Handler
[type] => ->
[args] => Array
(
[0] => Failure in changing password for
Postfix Admin server: Authentication failed.
[1] => horde.error
)
)
)
[previous:Exception:private] =>
)
thanks
Petr