Thanks for the reply! They would be pretty much be sharing the services. Just need some different layouts and the user backend is different. It's a tradeoff anyway but wondering if it would be easier to configure a single CAS to serve both purposes (or if it's even possible?) or have separate instances (easier? but lots of duplicate configuration...).
BR, Tom On Tuesday, 22 December 2015 13:55:28 UTC+2, wgthom wrote: > > Are the two org related in any way? Will they share CAS enabled services > or other IAM services? > > If not, you'll most likely just want to deploy two independent CAS > instances. > > Best, > Bill > > > > On Tue, Dec 22, 2015 at 5:54 AM, Tom Andersson <[email protected] > <javascript:>> wrote: > >> Hi, >> >> As a high level requirement we have a case where we would have two >> different organizations needing CAS services. They differentiate mainly in >> >> - Web layouts >> - Authentication backend >> >> Is there a best practice for handling this kind of scenario other than >> having separate CAS instances for both organizations? >> >> Thank you in advance for any pointers. >> Tom >> >> -- >> You received this message because you are subscribed to the Google Groups >> "CAS Community" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> Visit this group at >> https://groups.google.com/a/apereo.org/group/cas-user/. >> > > -- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/.
