Does anyone have thoughts about using wildcards in server names for SSL Certificates with CAS? For instances, a certificate with *.yourdomain.com will presumably secure email.yourdomain.com, test.yourdomain.com, production.yourdomain.com or for that matter cas.yourdomain.com. Our liaison for the Certification Authority (CA) is urging us to adopt this "wildcard" policy as a possible cost saving measure to get just one wildcard certificate for all the servers if we have to adopt SSL. I am pretty sure CAS can either handle this out-of-the-box (YES? HOW?) or I can extend the open source API to do so. That is less of a concern for me than right now than, should I do this? Therefore I am floating this balloon. Any pros/cons? Thanks, Uday Kari
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
