I understood the request was to completely merge them so that they share the same context root.
I see it as a lot of benefits of using CAS for our applications are lost doing that. Besides single sign on between different apps not working, there would then be multiple entrances to our applications, which one reason on group decided on CAS two years ago was that we could have only one entrance to protect. It seems if you want the login t be inside the application then there is no reason to use CAS, as the login using TGT and ST is meant to handle this architecture of a different application running it, and would be unnecessary if you want login to be part of the application. There may be other benefits of CAS we would loose embedding them together. I appreciate any thoughts and opinions about how this would affect the applications, security, functionality, etc. ________________________________ From: [email protected] <[email protected]> on behalf of William <[email protected]> Sent: Monday, February 8, 2016 3:55 PM To: CAS Community Cc: Nancy Snoke Subject: [cas-user] Re: embedding cas in an app Nancy, When you say "embed CAS inside an application" do you mean have CAS running along side a separate application in the same application server instance? Or do you mean completely merge the applications together so they share the same context root? Regards. -- 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]<mailto:[email protected]>. 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/.
