[Tickets #4799] hordeauth not working when imp invoked directly
bugs@bugs.horde.org
bugs at bugs.horde.org
Mon Dec 18 12:54:37 PST 2006
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/?id=4799
-----------------------------------------------------------------------
Ticket | 4799
Created By | liamr at deathstar.org
Summary | hordeauth not working when imp invoked directly
Queue | IMP
Version | HEAD
Type | Bug
State | Unconfirmed
Priority | 1. Low
Owners |
+New Attachment | cosign.php
-----------------------------------------------------------------------
liamr at deathstar.org (2006-12-18 12:54) wrote:
We use a modified version of the Horde "auto" authenticator that sets the
horde user name to the the value of $_SERVER[ 'REMOTE_USER' ] (which is
set by our SSO).
In imp/config/server.php, we've configured hordeauth to be true (we've
also tried 'full').
$servers['umce'] = array(
'name' => 'umce IMAP Service',
'server' => 'localhost',
'hordeauth' => true,
'protocol' => 'imap/notls',
'port' => 8143,
'maildomain' => 'umich.edu',
'smtphost' => 'smtp.mail.umich.edu',
'smtpport' => 25,
'realm' => '',
'preferred' => array( 'dev.mail.umich.edu' ),
'admin' => array(
'params' => array(
'login' => 'cyrus',
'password' => 'cyrus_pass',
'userhierarchy' => 'user/',
'protocol' => 'imap/notls',
'hostspec' => 'localhost',
'port' => 8143
)
),
'quota' => array(
'driver' => 'cyrus',
'params' => array(),
),
'acl' => array(
'driver' => 'rfc2086',
),
);
In horde/config/prefs.php, we've set initial_application to "imp" by
default.
Users going to https://dev.mail.umich.edu/horde/ are presented with their
inbox. As expected, we see this redirect in the location bar...
https://dev.mail.umich.edu/horde/imp/redirect.php?actionID=login&autologin=1&server_key=umce
Users going to https://dev.mail.umich.edu/horde/imp/ are presented with
the "Welcome to Mail" login screen.
Traditionally (Horde 3.1.3 / IMP 4.1.3, Horde 3.0.12 / IMP 4.0.5), both
/horde/ and /horde/imp/ will get passed through the transparent login
process and end up in the user's email box.
More information about the bugs
mailing list