| Summary | Implement authentication driver stack in composite authentication |
| Queue | Horde Base |
| Queue Version | Git master |
| Type | Enhancement |
| State | Accepted |
| Priority | 1. Low |
| Owners | |
| Requester | dom.lalot (at) gmail (dot) com |
| Created | 05/10/2011 (5118 days ago) |
| Due | |
| Updated | 05/20/2011 (5108 days ago) |
| Assigned | |
| Resolved | |
| Milestone | |
| Patch | No |
Summary ⇒ Implement authentication driver stack in composite authentication
State ⇒ Accepted
Version ⇒ Git master
drivers in the composite driver. Or to even implement a separate stack
authentication driver. This driver would try to authenticate the user
against all sub-drivers until it succeeds.
Using a different authentication driver for RPC authentification is
already possible by picking a driver configuration depending on
$_SERVER['PHP_SELF'].
Queue ⇒ Horde Base
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Synchronization
Summary ⇒ auth driver should be choosen in config
Type ⇒ Enhancement
State ⇒ New
Sometimes, using some auth drivers, rpc.php is enable to authenticate
as the auth method is not supported. For example SSO systems like
shibboleth that transmit only the username and don't send passwords to
horde.
Then we should say:
rpc driver is something else as in composite driver.
http://permalink.gmane.org/gmane.comp.horde.user/24352
Thanks
Dom