based on your input one more question:
Can you provide a ScreenShot of your About-Page of IS?
The Entrust IAIK library bundled to the IntegrationServer does not support TLS v1.1 and TLS v1.2.
TLS v1.1 and TLS v1.2 will be only available when IS runs in JVM 7 or 8, but not in JVM 6 or lower.
Additionally, TLS v1.1 and TLS v1.2 require JSSE mode instead of Entrust mode.
Here is a sample of the complete SSL/TLS-Settings when disabling SSLv2 and SSLv3 completely and only allow TLS regardless of version:
The first 2 entries refer to the protocol versions of JSSE and the other ones refer to the Entrust IAIK lib, where ‘tls’ stands for TLS v1.0, which is the maximum here.
The “watt.net.ssl.client.useJSSE=true” tells the IS to use JSSE for outgoing connections to any other servers.
If you want to disable TLS v1.0 and TLS v1.1, just remove them from the list of allowed protocols.
When the above settings are missing in your server.cnf, you can add them by editing the “Extended Settings” section in IS Admin UI under “Settings”. But these might not be taken into account as long as you do not have to corresponding Fix applied to your IS.
When you are hosting an HTTPS-Port in your IS, make sure it is configured to use JSSE as well for incoming connections.
Please check on Empower (https://empower.softwareag.com) for articles related to the POODLE SSL vulnerability.
I am not sure if there is a fix available for 6.5 to work around this vulnerability or to use JVM 7 with 6.5.