[imp] Login with Chrome not working

Bernhard (Mailinglist) bernhard_ml at drschierl.at
Thu Jun 6 20:19:18 UTC 2013


On 2013-06-06 22:13, Bernhard Schierl wrote:
> On 2013-06-06 21:33, John H. Bennett III wrote:
>> Quoting "Bernhard (Mailinglist)" <bernhard_ml at drschierl.at>:
>>
>>> Hi there,
>>>
>>> I upgraded few weeks ago from Horde 5.0.3 to 5.0.5, and today to 5.1
>>> (problem still exists).
>>>
>>> Horde is configured to use IMAP as authentication backend. Which is
>>> working without problems so fare.
>>> After the upgrade to 5.0.5 (later 5.1), I was not able to use Chrome
>>> (Browser) again to login. The login screen just accepts the user and
>>> pass and goes back to the login screen.
>>> This only happens with Chrome. I tried to delete all cookies, problem
>>> still exists.
>>>
>>> Checking the logfiles a get the following error:
>>>
>>> HORDE: [imp] Login success for user at user.com (Horde user user at user.com)
>>> [xx.xx.xx.xx] to {localhost:143 [imap]} [pid 20961 on line 157 of
>>> "/var/www/groupware/imp/lib/Auth.php"]
>>>
>>> HORDE: [horde] Login success for user at user.com [xx.xx.xx.xx] to horde.
>>> [pid 20838 on line 171 of "/path to grouware/login.php"]
>>>
>>> HORDE: User is not authorized for imp [pid 20838 on line 267 of
>>> "/usr/share/php/Horde/Registry.php"]
>>>
>>> I assume that the first line shows, that authentication with IMAP Server
>>> works. Also second line of the error message. Third line shows, that
>>> registration to Horde didn't work.
>>> These errors don't appear, if I use Internet Explorer (I don't use it)
>>> or Firefox.
>>> Since login with Chrome produces errors in the logfiles, I assume that
>>> this issue could be related to IMP and not Chrome.
>>>
>>> Google search shows, that there are some browser issues, but mainly with
>>> FF or others not Chrome.
>>>
>>>
>>> Anyone, who have similar problems?
>>>
>>> Bernhard
>> Hi Bernhard,
>>
>> I use chrome for testing H5, and periodically is this same error.  You
>> need to clear the browser cache, then you should be able to login. 
>> That's what fixes it for me every time.
>>
>> Regards,
>>
>> John
>>
>>
>>
>> John, you were right. It was I cookie issue. I solved it.
> Thank You.
> Bernhard
>



More information about the imp mailing list