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

Search Results: 3 of 27 [ <<First <Prev Next> Last>> ] [ Return to Search Results ]

* Your Email Address
* Spam protection	Enter the letters below: . ..__ \ / . __ \|\ \|[__) >< \|/ ` \| \\|\| \/ \\__\|\__.
Comment	> 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').
Attachment
Watch this ticket