Tickets :: [#11411] User is not authorized for horde

6.0.0-alpha14

7/2/25

Summary	User is not authorized for horde
Queue	Horde Base
Queue Version	5.0.0beta5
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	hostmaster (at) ip6 (dot) li
Created	09/08/2012 (4680 days ago)
Due
Updated	07/11/2013 (4374 days ago)
Assigned
Resolved	09/10/2012 (4678 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

07/11/2013 01:58:49 AM	lfbm (dot) andamentos (at) gmail (dot) com	Comment #8	Reply to this comment
I got the same behavior after upgrading to 5.0.1 , after trying reinstalling etc I finally discovered that if I change the cookie path by something other than '/' I got the error (Which may not be a bug but IS a big hurdle) In my case I have $conf[cookie][path] as '/' and I get the error anyway. Horde 5.1.1. Just found out this is caused by a google bot crawler trying to access rampage.php on my horde website: http://marc.info/?l=horde&m=137350543201886&w=2

07/10/2013 11:20:04 PM	lfbm (dot) andamentos (at) gmail (dot) com	Comment #7	Reply to this comment
I got the same behavior after upgrading to 5.0.1 , after trying reinstalling etc I finally discovered that if I change the cookie path by something other than '/' I got the error (Which may not be a bug but IS a big hurdle) In my case I have $conf[cookie][path] as '/' and I get the error anyway. Horde 5.1.1.

03/06/2013 06:04:50 PM	vtourneyrie (at) vinceti (dot) com	Comment #6	Reply to this comment
I got the same behavior after upgrading to 5.0.1 , after trying reinstalling etc I finally discovered that if I change the cookie path by something other than '/' I got the error (Which may not be a bug but IS a big hurdle)

02/27/2013 07:13:59 AM	cyx (at) gmx (dot) at	Comment #5	Reply to this comment
same problem here, after upgrade from horde 5.0.2 to 5.0.3 i see only HORDE: User is not authorized for horde [pid 441 on line 259 of ... 5.0.2 was running fine, any hints ? Havee You solved this prob, have the same ....

02/12/2013 08:16:06 AM	nschmidt (at) df (dot) eu	Comment #4	Reply to this comment
same problem here, after upgrade from horde 5.0.2 to 5.0.3 i see only HORDE: User is not authorized for horde [pid 441 on line 259 of ... 5.0.2 was running fine, any hints ?

09/15/2012 02:51:23 PM	mariecamps (at) gmail (dot) com	Comment #3	Reply to this comment
You cannot use "hordauth" and IMP application authentication at the same time. Please use the mailing list to ask for support. http://www.horde.org/mail/ contains a list of all available mailing lists. I have the same problem and I had setup hordeauth = false

09/10/2012 09:40:01 AM	Jan Schneider	Comment #2 State ⇒ Not A Bug	Reply to this comment
You cannot use "hordauth" and IMP application authentication at the same time. Please use the mailing list to ask for support. http://www.horde.org/mail/ contains a list of all available mailing lists.

09/08/2012 05:47:04 PM	hostmaster (at) ip6 (dot) li	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ User is not authorized for horde Queue ⇒ Horde Base Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
horde5 is configured to use imp for login. After login following appears in syslog: Sep 8 19:40:45 webmail-test HORDE: [horde] Login success for xxx@example.net [192.168.116.22] to horde. [pid 3279 on line 160 of "/var/www/test/login.php"] Sep 8 19:40:45 webmail-test HORDE: User is not authorized for horde [pid 3279 on line 266 of "/usr/share/php/Horde/Registry.php"] backends.local.php: <?php $servers['imap'] = array( // ENABLED by default 'disabled' => false, 'name' => 'IMAP Server', 'hostspec' => '192.168.116.2', 'hordeauth' => 'full', 'protocol' => 'imap', 'port' => 143, 'secure' => 'false', 'maildomain' => '', 'quota' => array( 'driver' => 'imap', 'params' => array( 'hide_when_unlimited' => true, 'unit' => 'MB' ) ), 'cache' => false, 'acl' => true, ); this backend.local.php works without any problems in a Horde 4 environment.