<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Aug 17, 2015 at 12:18 PM, Stian Thorgersen <span dir="ltr"><<a href="mailto:stian@redhat.com" target="_blank">stian@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
> However it might be a good idea to include a generic HTTP/REST implementation<br>
> which you could configure through the admin interface to deliver SMS<br>
> messages to any service supporting HTTP? I'm pretty sure this would satisfy<br>
> most users.<br>
<br>
</span>Not sure how that would work. AFAIK SMS providers have their own proprietary rest endpoints as well as authentication mechanisms so I don't see how we could create a generic implementation.<br><div class="HOEnZb"><div> </div></div></blockquote><div><br></div><div>You would need to implement a template mechanism where the Keycloak data (for example the recipient number and message text) is provided as keywords, and the admin defines the template utilizing those keywords. It would be a good idea to allow choosing between POST and GET.<br><br></div><div>For example Twilio supports a simple HTTP POST operation to delivery SMS messages through their API:<br><a href="https://www.twilio.com/docs/api/rest/sending-messages">https://www.twilio.com/docs/api/rest/sending-messages</a><br><br></div><div>Many operators and service providers use a similar mechanism. Often the authentication is just a simple token which needs to be included in the request.<br></div><div><br></div><div>Best regards,<br></div><div>Thomas <br></div></div>
</div></div>