I'm facing an unusual situation, I hope you can clarify this for me.
We manage some applications that are accessible through HTTPS requests on port 443 of our server X.
We have a new client that is also supposed to reach us through our 443 port on server X. However the client is going to use some kind of Load Balancer (proxy + snat according to them) to do that.
So that the Load Balancer can connect to us, the client is requiring our pair of Public Certificate + Private key, otherwise the Load Balancer would reset connections with us due to key pairs mismatch.
This is completely nonsense for me as the private should be simply private, I can't share it. It is against every security policy I know.
Curious part is that they provided some documentation that seems to state exactly this. This is the link:
It seems they use some technology called Big IP and it requires the private key according to this statement on the above link:
Recommended Actions You can rectify this error by configuring the affected SSL profiles with the certificate key pair that is presented by the destination server. To do this, perform the following procedures ...
Has any one you faced any similar situation to this?
Even their technology really requires it, I'm not aware about any 'API' provided by HTTPS that would handle traffic previously ciphered by a Load Balancer, so I'm pretty confuse.
Every kind of clarification is useful. Thanks everyone.