[Tickets #10980] Re: Create the possibility of two alternative authentication modules

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10980
------------------------------------------------------------------------------
  Ticket             | 10980
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Create the possibility of two alternative
                     | authentication modules
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Enhancement
-State              | New
+State              | Feedback
-Priority           | 2. Medium
+Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2012-02-12 17:29) wrote:

Reviewing this... my feeling is this is a bit too-site specific to be  
useful to maintain/distribute in the main code base.

I would be more receptive to a driver that allows a queue of  
authentication backends and would traverse the list of backends until  
authenticated.  But this would be a very simple looping idea: the  
'single_validation' config could not be a part of this. That is the  
part that is too site-specific (not to mention that this driver is  
lacking all details on how the admin auth methods would work).

The good news - this should be easy enough for you to maintain  
locally.  You just need to name your Auth class to something that can  
be autoloaded, and then just set $conf['auth']['driver'] in  
horde/config/conf.php to the full name of your Auth class (e.g.  
'Horde_Auth_Foo').