<div dir="ltr">That could be an addition. We'd need a global hostname configured outside of the realm, but being able to override on a realm level could be good.</div><div class="gmail_extra"><br><div class="gmail_quote">On 22 October 2015 at 09:02, Thomas Raehalme <span dir="ltr"><<a href="mailto:thomas.raehalme@aitiofinland.com" target="_blank">thomas.raehalme@aitiofinland.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Thu, Oct 22, 2015 at 9:42 AM, Stian Thorgersen <span dir="ltr"><<a href="mailto:sthorger@redhat.com" target="_blank">sthorger@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">The simplest solution to this would be to add an option to set the hostname for the server. This would be configured in keycloak-server.json, but we'd also support setting it with a system property. Default would be to use the request-url as we do now, but once specified we would not use the request-url anymore and always use the configured hostname as the base URL.<br></div>
<br></blockquote><div><br></div></span><div>How about making it an option in the realm configuration? It would allow you to brand the realm just like with themes. <br><br></div><div>Best regards,<br></div><div>Thomas<br></div><div><br> </div><div><br> </div></div><br></div></div>
</blockquote></div><br></div>