Issue #542 has been reported by Jonathan Clarke. ---------------------------------------- Feature #542: Support other SMS sending tools http://tools.lsc-project.org/issues/542
Author: Jonathan Clarke Status: New Priority: Normal Assigned to: Category: Self Service Password Target version: self-service-password-? I note that SSP 0.8 introduces the possibility to send a confirmation code by SMS, enabling 2 factor-authentication for password changes (see #354). This is very nice. However, the feature currently only supports sending via a SMTP-to-SMS system, in other words sending an email. It would be great to implement an archictecture that allows to enable using SMS, and then choose a "provider" for actually sending the SMS: either the existing SMTP-to-SMS provider, or other, specific providers. My particular use case is to support the OVH provider, who offer an API that is easily accessible from PHP (see http://www.ovh.com/soapi/fr/?method=telephonySmsSend for a PHP code generator). The parameters for this are basically account ID, password, sending number. But in some cases you may have to provide an extra username (ie, the account at OVH has several users). My point here is that each provider may have different settings required. This ticket could lead to the implementation of that provider, of course, but I think it is important to first consider the architecture around this - how can we support several providers, what config parameters would be used, etc? And ideas? -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________ ltb-dev mailing list [email protected] http://lists.ltb-project.org/listinfo/ltb-dev
