Hi
We recently had an application server updated such that it now runs TLS 1.2 (high security level).
Unfortunately now the copious number of protocols I've written that heavily use the HTTP Connector component to trigger GET / PUT / PUSH etc web services no longer function since a connection to the application server can not be made.
I think this is due to the HTTP Connector component being tied to TLS1.0 with no possibility to configure it to utilize any other https protocol.
I assume this will become more prevalent as more and more services upgrade to TLS 1.2. It seems an oversight that the HTTP Connector component can't support it.
Has anyone else encountered a similar issue - what workarounds, if any, helped to address the problem?
@Biovia - please confirm if the HTTP Connector component cannot indeed support web service requests to a server running TLS 1.2. If it can then clearly we're doing something wrong on our end.
Many thanks,
Tristan
Running 2017 R2
We recently had an application server updated such that it now runs TLS 1.2 (high security level).
Unfortunately now the copious number of protocols I've written that heavily use the HTTP Connector component to trigger GET / PUT / PUSH etc web services no longer function since a connection to the application server can not be made.
I think this is due to the HTTP Connector component being tied to TLS1.0 with no possibility to configure it to utilize any other https protocol.
I assume this will become more prevalent as more and more services upgrade to TLS 1.2. It seems an oversight that the HTTP Connector component can't support it.
Has anyone else encountered a similar issue - what workarounds, if any, helped to address the problem?
@Biovia - please confirm if the HTTP Connector component cannot indeed support web service requests to a server running TLS 1.2. If it can then clearly we're doing something wrong on our end.
Many thanks,
Tristan
Running 2017 R2
