We are running Content server web servers behind a Load balancer that balances traffic between two CS Web Servers. We are also using HTTS in that environment and we are trying to migrate the enviorment to use HTTPS instead of HTTP.
We have already configured the appropriate web.config files to support https, and we have updated IIS to use an SSL Certificate for the Load balanced URL (e.g. myserver.mydomain.com). However we are having issues with the requesting application complaining about SSL certificates. What I had noticed when running the https://myserver.mydomain.com/cws/DocumentManagement.svc?wsdl command, was that although the command is referencing the Load balancer (i.e. nyserver.mydomain.com) the XML returned references URL of one of my load balanced servers (e.g. cs1.mydomain.com) and NOT the load balancer URL (which is configured Sticky Session).
<xsd:schema targetNamespace="urn:DocMan.service.livelink.opentext.com/Imports">
<xsd:import schemaLocation="https://cs1.mydomain.com/cws/DocumentManagement.svc?xsd=xsd0" namespace="urn:DocMan.service.livelink.opentext.com"/>
<xsd:import schemaLocation="https://cs1.mydomain.com/cws/DocumentManagement.svc?xsd=xsd1" namespace="urn:api.ecm.opentext.com"/>
<xsd:import schemaLocation="https://cs1.mydomain.com/cws/DocumentManagement.svc?xsd=xsd2" namespace="urn:Core.service.livelink.opentext.com"/>
</xsd:schema>
This appears to be causing problems because the SSL certificate for myserver.mydomain.com is on the load balancer on each of the the web servers. yet the returned XML is pointing the requesting application to use the Web server currently processing the request (i.e. cs1.mydomain.com) for the schema location. Accordingly, if the requesing application tries to use the https:/cs1.mydomain.com URL it will be presented with a Certificate that does not match the URL.
- How do I address this issue?
- is there any way to change the wsdl xml to use the Load balancer URL instead of the Web server URL?
