<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Aug 18, 2015 at 3:35 PM, Bill Burke <span dir="ltr"><<a href="mailto:bburke@redhat.com" target="_blank">bburke@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></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
Sure, the interface would be simple to implement, but nevertheless it<br>
requires a customization to the install and Keycloak no longer works<br>
out-of-the-box.<br>
<br>
I'm not saying the interface should not be there, but that it would be<br>
great to also have a simple HTTP implementation available.<br>
<br>
</span></blockquote>
<br>
>From what I've researched, most of these simple services you have to pay for. There's an OSS SMS proxy and library you can integrate and test. But that's it.</blockquote><div><br></div><div>In my opinion a perfect solution would be a template/keywords based HTTP implementation where the user can configure endpoint URL and Keycloak will find-and-replace keywords such as ${phone} and ${message}. That's easy to test.<br><br></div><div>Then whoever wants to use SMS needs to purchase a service which provides simple enough HTTP API, or write their own implementation of the Keycloak interface Stian suggested.<br></div><div><br></div><div>Best regards,<br></div><div>Thomas <br></div></div>
</div></div>