> This is a product that we ship to customers. Customers can install multiple > instances of this product in their environment to scale out.
Simply put: CAS is not a federated SSO product. Your options: - Implement federated SSO in CAS. If Shibboleth is any indication the return on investment would be (profoundly) negative for your use case. - Creative hack where CAS instances trust one another based. An authentication handler that could query another CAS server for authenticated state of a user comes to mind. - Simply change the way you distribute your product such that the CAS server component can be installed just once for N installations such that all share a single logical CAS instance. Honestly the last option sounds like the best one. Based on what you've shared, all installations should ideally share a single CAS server anyway. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
