The certificate within the tomcat keystore is self-signed by SunSystems. Therefore, the first time Windows Internet Explorer opens a secure page using the certificate, a message displays indicating that the certificate is not known to be trusted, and that the certificate organisation does not match the web site name.
You may want to replace the certificate with one of your own, particularly if the web server is exposed to external users. Refer to your Tomcat documentation and the Java keytool application for further information.
Enabling Secure Web PagesBy default, the Tomcat server has secure sockets enabled. To use a secure connection, use the following URL:
https://localhost:8443/ssc/The padlock icon on the browser status bar indicates secure connections.
The Tomcat secure connection is configured in the server.xml file in the <http10connector> tag that has secure="true". Elements of this tag specify the port number, keystore file and password. After changing any of these elements you must update the server.xml file. Details on how to update this file are documented by comments in the server.xml file and in the Tomcat documentation at:
http://www.apache.orgEnabling Secure SOAPBecause SOAP messages pass over normal http/s type connections, secure web pages imply secure SOAP. To access secure SOAP you must change the SOAP server URL in your client code to:
https://server:8443/ssc/servlet/SUGSoapThe soap.server_url property specifies this for SSC components.
Enabling Secure RMIJava Remote Method Invocation (RMI) is the network protocol used by the SSC client applications (Transfer Desk, Transfer Profile Designer etc.) to communicate with the SSC server. RMI can be configured to run over secure sockets by setting the security.secure_sockets flag to true in the SSC properties using the property editor. This property needs to be set on both
client and server machines. The SSC server must be restarted in order for this change to take effect.
Only registered users can write comments.
Please login or register.