I have a site setup on IIS that uses HTTPS. This site has an SSL cert binded using the severs Fully Qualified Domain Name. This site is suppose to be accessed by a 3rd party vendor. Basically we have a router on our corporate network from 1 company(lets calls this company A) and then this company A has a router on their side that allows another company(Company B) to access their network. Company A has whitelisted our IP address and has opened port 443 to allow our connection to reach Company B. Now Company A and Company B only know our IP Address not our server's fully qualified domain name. When Company B attempts to connect using https://10.x.x.x they are receiving a trust relationship error which makes sense since our ssl cert is based on the server name NOT the IP address. This server's ip/url is not meant for public use. Only internal. From my understanding you can't create an SSL cert based on an IP address so I am kind of stuck here. What are we suppose to do to resolve this ssl error if company A and B only know our IP Address? Any help is appreciated!
↧