[Tickets #3170] RESOLVED: Update to login.php to load preferred backend if it doesn't require authentication

bugs@bugs.horde.org bugs at bugs.horde.org
Sun Jan 1 23:42:18 PST 2006


Ticket URL: http://bugs.horde.org/ticket/?id=3170
 Ticket             | 3170
 Updated By         | dorm at dorm.org
 Summary            | Update to login.php to load preferred backend if it doesn't require authentication
 Queue              | Gollem
 Version            | HEAD
 State              | Rejected
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | Michael Slusarz

dorm at dorm.org (2006-01-01 23:42) wrote:

The 'preferred' setting makes sense to me, that is it just for the default
selection on the login page.

But what about the case where all configured backends do not require
authentication?  This is what I'm running into.  I have two 'file' backends
which map to different directories.  Neither requires authentication, so
neither should display a login screen.

But with the current code, if I click on the 'File Manager' icon in the
Horde tree, then instead of my 'preferred' backend getting loaded, I get the
login screen for that backend.  Since it doesn't require authentication, all
it is is a single "Login" button in the frame.  After clicking this button
the file listing for that preferred backend is displayed correctly.  But I
don't think users should have to click that Login button, since no
authentication is required.

But I see your point now, that if multiple backends are configured and some
require auth but the preferred does not, then users would automatically be
sent to the preferred backend and not even given the chance to log in to a
non-preferred one.

I'm not sure what is the best way to approach this.  But I also don't think
that the behavior I'm seeing is appropriate given my configuration.  

If you have another way you'd like to see this solved, I'd be happy to make
the changes and submit new patches.


More information about the bugs mailing list