[horde] Initial authentication problems

[Guil Barros]

i fixed this by installing imp, copying over an imp config i already had,
changing my horde auth to imp/application. That way i could login to horde and
recreate its config file through its web interface.

everything worked from there. I do wish that someone had told me the "kosher"
way of doing this though...

-guil

Quoting Josh Endries <jendries at pragmeta.com>:

> Similar to two other (unresolved) posts I found in the archive, I'm running
> into the same problem. I just installed the latest CVS snapshot and I'm
> getting this error:
>
> Feb 11 11:53:53 HORDE [error] [horde] FAILED LOGIN for admin [192.168.0.16]
> to Horde [on line 93 of "/usr/local/www/data-dist/horde/login.php"]
> Feb 11 11:53:53 HORDE [debug] [] User  does not have READ permission for
> horde [on line 637 of "/usr/local/www/data-dist/horde/lib/Registry.php"]
>
> I'm pretty sure the config is correct, and it's sending the SQL correctly:
>
> Feb 11 11:53:53 horde postgres[26738]: [1-1] LOG:  connection received:
> host=localhost port=1134
> Feb 11 11:53:53 horde postgres[26738]: [2-1] LOG:  connection authorized:
> user=horde database=horde
> Feb 11 11:53:53 horde postgres[26738]: [3-1] LOG:  statement: SELECT
> user_pass FROM horde_users WHERE user_uid = 'admin'
> Feb 11 11:53:53 horde postgres[26738]: [4-1] LOG:  duration: 31.272 ms
> statement: SELECT user_pass FROM horde_users WHERE user_uid = 'admin'
>
> That SQL does get the correct MD5 password. My PHP does have mcrypt, though
> I don't know if that matters for this. I ran the simple script to create
> an initial admin user and I'm just trying to login via /horde using
> admin/admin, which is the correct data in the db. Now one archived post
> asked a question about setting permissions on installed applications,
> which I don't understand. I installed everything by default; I didn't
> change any permissions anywhere, so unless things are disabled by default,
> it should work (I would think). This is just a Horde install, no modules
> yet, I'm just testing it step-by-step. As far as I can tell it's a Horde
> problem or a config problem. Any ideas?
>
> Thanks,
> Josh
> --
> Horde mailing list - Join the hunt: http://horde.org/bounties/#horde
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org