[horde] Help! Followed the FAQ and still get 'User is not authorized'

Steffen skhorde at smail.inf.fh-bonn-rhein-sieg.de
Tue Mar 25 08:55:09 UTC 2014


On Mon, 24 Mar 2014, David Benfell wrote:

> Mar 24 03:13:26 munich HORDE: [horde] Login success for benfell
> [2601:9:3a00:6c:2216:d8ff:fef8:89a4] to horde. [pid 6297 on line 150 of
> "/usr/share/horde/login.php"]
> Mar 24 03:13:34 munich HORDE: [horde] Login success for benfell
> [2601:9:3a00:6c:2216:d8ff:fef8:89a4] to imp. [pid 6318 on line 150 of
> "/usr/share/horde/login.php"]
> Mar 24 03:13:35 munich HORDE: [imp] Login success for benfell (Horde user
> benfell) [2601:9:3a00:6c:2216:d8ff:fef8:89a4] to {localhost:143 [imap]}
> [pid 6298 on line 157 of "/usr/share/horde/imp/lib/Auth.php"]
> Mar 24 03:16:59 munich HORDE: [horde] User benfell
> [2601:9:3a00:6c:2216:d8ff:fef8:89a4] logged out of Horde [pid 5534 on line
> 102 of "/usr/share/horde/login.php"]
> Mar 24 03:17:25 munich HORDE: [horde] User
> [2601:9:3a00:6c:2216:d8ff:fef8:89a4] logged out of Horde [pid 5534 on line
> 102 of "/usr/share/horde/login.php"]

> This is on CentOS release 6.5 (Final), a 64-bit system. It just won't let
> go. The authorization method is IMAP with dovecot on the same machine (but
> it looks to me like that part is working). I've flushed my cookies and
> followed the FAQ.

Did you copied the config from somewhere, maybe migrated from an earlier 
version?
I had such problem in the beginning myself. I've thrown away my migrated 
H3 config and re-created from scratch, one setting after another. There had 
been a thread about cache timeouts some time ago, I think the settings in 
question were:
$conf['session']['timeout']
$conf['session']['max_time']
Someone had stuff there, which rendered the session management useless.

With WLAN clients I have the problem that they get new IPs sometimes and 
get refused by Horde. Speaking of cookies, you've said you flushed them, 
re-check that you do not have forbidden cookies for sub-domains or
something like that. I do have seen problems with Mozilla when the users 
switched from H3 to H5 their old profile failed, a new one worked fine.

-- 
Steffen


More information about the horde mailing list