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	> Dear Dev-Team, > > if the format of my request/patch does not comply, please be patient > with someone new to it. I will be happy to correct any mistakes > pointed out. > > This is a stacking auth module (cf. Horde_Auth_Composite), which > allows to use two authentication modules. The main usecase is to > either validate the pwd against two different backends, or to > validate against at least one backend. (patch attached) > > This is to facilitate the integration of a one-time-password scheme > under development. The user would choose which password to enter > (permanent vs. otp) and it could be processed. > > An example configuration usecase would look like this: > $conf['auth']['driver'] = 'composite'; > $conf['auth']['params']['admin_driver']['driver'] = 'sql'; > $conf['auth']['params']['auth_driver']['driver'] = 'dual'; > $conf['auth']['params']['auth_driver']['params']['single_validation'] = true; > $conf['auth']['params']['auth_driver']['params']['auth1_driver']['driver'] = > 'sql'; > $conf['auth']['params']['auth_driver']['params']['auth2_driver']['driver'] = > 'one-time-password-mechanism' > > Any feedback on implementations and/or enhancements very appreciated. > > Best regards, > Carl > > PS: Priority is medium, as I would like to build other features on > top of this one. Please correct it, if it is too high.
Attachment
Watch this ticket