TLS 1.2 - Server 2008 Std (NOT R2) - in IIS

IIS server running Server 2008 std (not R2)

with a lot of sites changing to use TLS 1.2 we are having a few intergration errors when trying to communicate with external APIs.

For example,   LinkedIn integration will only work with TLS 1.2.

As my server has server 2008 std non r2 I cannot enable TLS 1.2

I do not have the option of upgrading the OS on the server...

But we have another server running r2 with tls 1.2 working! it possible to create some sort of reverse proxy rule to redirect requests to the 3rd party via the other webserver which has tls 1.2 enabled?

( Note: I cant just put my sites directly on the 2008 R2 webserver)

I tried some url rewrite rule but couldn't get it working...

any help would be appreciated...
Who is Participating?
kevinhsiehConnect With a Mentor Commented:
You might be able to setup a reverse proxy like you would for one of your web servers, but instead of proxying incoming requests you would turn the proxy around and publish the sales force servers to your internal network and use maybe a hosts entry on your Windows 2008 server to point the sales force hosts at your proxy server.

Windows 2008 is in extended support and is like running Windows Vista, and is 3 major OS versions behind. You'll need to upgrade it eventually, and I think that you are seeing some issues where sooner may be better than later. :-)
btanConnect With a Mentor Exec ConsultantCommented:
The redirect has to be redirected before the key exchange start eles the SSL session cannot be maintain as redirection thereafter will break the session. Some application delivery controller does this full TLS proxy (e.g.  manage the client SSL, terminate and then manage Server SSL , as a whole does SSL offload) and balance (with re-encrypt based on Server SSL profile) to the selected web server backend e.g in F5 LTM @
It also flagged in their forum to do before handshake on option that may be viable @

But to do simply redirect based on TLS1.2 you need to packet inspect into the packet byte to determine the version though which I see IIS URL Rewrite Module may not be possible. There may need to have some module plugin that does that...below is some useful example but not specific to your use case though
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.