> I am also looking for other non-cas solution for my situation.
There is a straightforward solution to your problem. Use a
certificate that makes use of the "Subject Alternative Name" field of
the X.509 certificate. You can have as many of those entries as you
want, one for each host name at which your application is available.
That will relieve browsers of the ominous warning messages. See
section "4.2.1.7 Subject Alternative Name" of
http://www.faqs.org/rfcs/rfc2459.html
for more information.
You should by all means use CAS if you truly have a need for single
sign-on, but from your post it sounds like you want a simple solution
to your certificate hostname mismatch problem. The SubjectAltName
field is the way to go in that case.
M
--
You are currently subscribed to
[hidden email] as:
[hidden email]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user