
Originally Posted by
harasta
Rob, thanks for advice and the example. But an error page and a load balancer are definitely dead ends. Believe me.
I have read all reactions in this thread again. And again I think of Luke's last advice:
> You would probably be better to look at making the CAS server itself more robust.
That's the point. Luke might have HW infrastructure on his mind. It would make sense. The CAS server should run on solid HW, simply because it is SSO service.
All I can do for users of my application is to let them enter thru an insecured page which checks out availability of services at first. If anything goes wrong after that, users should return to this well-known page and should contact an administrator.
Thank you all for kind following of my thoughts.
Best regards,
Vladimir