| Summary | HORDE User is not authorized for horde |
| Queue | Horde Base |
| Queue Version | 5.0.4 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | vtourneyrie (at) vinceti (dot) com |
| Created | 03/12/2013 (4495 days ago) |
| Due | |
| Updated | 04/18/2013 (4458 days ago) |
| Assigned | |
| Resolved | 03/12/2013 (4495 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
admin user. I have horde running on Apache in an Alias path called
"/webmail" (i.e., the home/login address for horde is
"https://www.mysite.com/webmail"). I have the horde cookie path set
to /webmail. On the underlying server, horde is installed in
/var/www/horde (i.e., in my Apache config for this site, /webmail is
an alias for /var/www/horde).
I use LDAP authentication, and I can log into dovecot IMAP or postfix
as any of my users, both of which use the same LDAP database for
authentication. And as I mentioned, my admin user can log into horde
just fine, and other than being designated in the horde prefs.php as
an admin user, this user is in all relevant respects identical to the
users who can't log in as far as I can tell (same LDAP object classes,
all relevant LDAP fields populated).
Is there a problem with this setup or is there something else causing
the "user not authorized for horde" message?
State ⇒ Not A Bug
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Base
Summary ⇒ HORDE User is not authorized for horde
Type ⇒ Bug
State ⇒ Unconfirmed
NOTICE: HORDE [horde] Login success for xx@xx [x,x,x,x] to horde.
[pid 21137 on line 163 of "/srv/www/htdocs/horde/login.php"]
EMERG: HORDE User is not authorized for horde [pid 21137 on line 259
of "/usr/share/php5/PEAR/Horde/Registry.php"]