<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 21, 2015 at 6:43 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 class=""></span>We originally took this route with Keycloak. The idea that Keycloak<br>
could be a SAAS...But we decided that the best way to deploy Keycloak in<br>
the cloud would be to create a cloud instance of Keycloak per<br>
organization. In Red Hat OpenShift terms: Keycloak would be a<br>
cartridge and the organization could opt to install it within their<br>
cloud account.<br>
<br>
The reason for this is to isolate one paying customer from a different<br>
one. You probably don't want them sharing database instances, IP<br>
addresses, etc.<br>
<br>
If that is not possible, we can discuss other possibilities. Right now<br>
though Realm is a completely isolated unit. Users belong to one realm<br>
and one realm only.<br></blockquote><div><br></div><div>I think you have the best of both worlds, ie. you can create multiple realms with a single Keycloak install to manage multiple customers, or you could install Keycloak for each customer separately as you describe above.<br></div><div><br></div><div>Now we app developers just need to figure out the best way to handle this on our side :-)<br><br></div><div>Best regards,<br></div><div>Thomas<br></div></div></div></div>