Connect CDC uses secure socket layer (SSL) Java classes for encrypted communications. The protocols used are compliant with Transport Layer Security (TLS) 1.2 and include 256 bit cipher suites.
To set the security and encryption option for the model in Connect CDC Director, from the context menu of the model, go to Model Properties and click the XML/Encryption tab.
Similarly, to set the option for the host that differs from the model in general, go to the Host Properties tab from the context menu of the host. The tab provides the same options with the addition of the model default option.
The Host Properties must specify encryption, if encryption was used to start the Connect CDC Listener during installation. If they do not match, connections are refused, that is, encrypted model connections to a non-encrypted Listener fail and vice versa.
The monitoring and control tools use whatever the model properties option is for security. For example, if the model has authentication and not encryption specified, then Connect CDC MonCon has the same security options enabled.
Encryption was set up in the Connect CDC Listener during installation. (See Installation Guide.) After installation is complete, re-install to change the security options.
If problems occur with SSL, check the following:
-
Installation should have placed certification file omnicert in the /kernel and /director directories. This file needs to reside in both to enable successful authentication.
-
The classpath set in omnient.ini must point to the correct location of these files: omni.jar, jsse.jar, jnet.jar, and jcert.jar.