This article goes through the steps to import a certificate into the Java Keystore ( cacerts ) file so JBoss can communicate via SSL / HTTPS to secure sites and URL's. You first need to acquire the public certificate or DER encoded binary X.509 (.CER) file to import. For more information on this see KB S139798
1) The first step in configuring SSL is to obtain an SSL certificate . This can either be a self-signed certificate or a certificate obtained through a trusted certificate authority. Note that self-signed certificates will encrypt the user data but will result in a warning message to end users that the certificate may not be valid.
ZMF for Eclipse 8.2 Patch 3 has removed the dependency on ZMF Web Services. This simplifies the installation and configuration process as well the set-up process for SSL connections.
ZMF REST Services Getting Started Guide, all secure communication functionality (i.e. SSL) associated with this processing on z/OS must be implemented using IBM's Application Transparent Transport Layer Security (AT-TLS). Some customers may have found and implemented other solutions that address their specific needs (e.g. the implementation of native Apache Tomcat SSL connectors). However, if problems are encountered
Notes: - Customer is not using SSL connections and all settings are appropriate for this. - The same users can connect successfully from the same client machines to the same ZMF Server using ZDD.
However, several customers also host their own homegrown, ZMF web services(ZMFWS)-based applications. Looking at the web services there is no ‘secure logon’/TLS/ SSL option available. This functionality needs to be added so that custom applications can also exploit the benefits of AT-TLS security.
Notes: - Reporting customer is not using SSL connections and all settings are appropriate for this. - The same users can connect successfully from the same client machines to the same ZMF Server using ZDD.
[1/10/17 14:12:51:416 CET] 00000012 SystemErr R javax.net. ssl .SSLException: SSLSocketFactory is null. This can occur if javax.net.ssl.SSLSocketFactory.getDefault() is called to create a socket and javax.net.ssl.* properties are not set.
