asha latha wrote: > Thank you for your response John. > > I removed those two lines from the server.xml. > > <Connector port="8443" maxHttpHeaderSize="8192" > maxThreads="150" minSpareThreads="25" maxSpareThreads="75" > enableLookups="false" disableUploadTimeout="true" > acceptCount="100" scheme="https" secure="true" > clientAuth="false" sslProtocol="TLS" > /> > Now I am not getting exceptions in tomcat. Excellent. > But when I try to open the SSL configuration by going to > https://localhost:8443/ > > I am getting the following error message . > > There is a problem with this website's security > certificate. > The security certificate presented by this website was not > issued by a trusted certificate authority. > > > > Security certificate problems may indicate an attempt to fool you or > intercept any data you send to the server. > > Do you have any idea what's going on? > Sounds like things are working fine.
Because you made a self-signed certificate, it's not automatically trusted by your browser and you get the warning. For a production service, you'll probably want to purchase an SSL certificate from a certificate authority (CA). There are lots of vendors: Verisign/Thawte, Comodo, GeoTrust, and many others. John _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
