: p
[javadoc] It is suggested the reader first review Getting Started with Secure Connections, as this document relies on the topics covered there.
[javadoc] ^
[javadoc] /builddir/build/BUILD/sblim-cim-client2-2.2.5-src/src/org/sblim/cimclient/doc-files/secure_indications.html:39: error: tag not allowed here:
[javadoc]
As described in Getting Started with Indications, indication delivery reverses the role of of HTTP client and server. The indication sender (typically the CIMOM) is now the HTTP client and the indication listener is the HTTP server.
[javadoc] ^
[javadoc] /builddir/build/BUILD/sblim-cim-client2-2.2.5-src/src/org/sblim/cimclient/doc-files/secure_indications.html:40: error: tag not allowed here:
[javadoc]
For SSL/TLS (HTTPS) connections, configuration of a keystore is optional for the HTTPS client. For a HTTPS server however, a keystore is mandatory. This is because the keystore contains the private key the server will use to initiate encryption for the connection. So we must configure a keystore to enable a secure indication listener.
[javadoc] ^
[javadoc] /builddir/build/BUILD/sblim-cim-client2-2.2.5-src/src/org/sblim/cimclient/doc-files/secure_indications.html:41: error: tag not allowed here:
[javadoc]
The keystore also contains the certificate the HTTPS server (i.e. the indication listener) will use to assert its identity. The HTTPS client (the indication sender or CIMOM) may optionally choose to verify the server cert against the contents of its own truststore.
[javadoc] ^
[javadoc] /builddir/build/BUILD/sblim-cim-client2-2.2.5-src/src/org/sblim/cimclient/doc-files/secure_indications.html:43: error: tag not allowed here:
[javadoc]
Similarly, the listener may choose to verify the certificate of the indication sender. To do this we need to additionally configure a truststore for the listener.
[javadoc] ^
[javadoc] /builddir/build/BUILD/sblim-cim-client2-2.2.5-src/src/org/sblim/cimclient/doc-files/secure_indications.html:45: error: self-closing element not allowed
[javadoc]