We did a similar approach but with individual DNS names directly to the machines themselves, so
> https://my.university.edu/portal/host1 > https://my.university.edu/portal/host2 would be in our case: > https://myServer1.university.edu/portal/CasProxyServlet > https://myServer2.university.edu/portal/CasProxyServlet while the serviceAddress would still be > https://my.university.edu/portal/ It's about the same, only different in network routing because we bypass the loadbalancer. In our approach we are using separate certificates on each individual server which makes it possible/requires to identify each sever separately (we use an own CA for that so it doesn't add any cost). However in our case you need to enable SSL on each individual server. -- Velpi _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
