Showing results for 
Search instead for 
Do you mean 

How to use GeoMedia Smart Client with HTTPS

by Technical Evangelist on ‎11-04-2015 11:09 PM - edited on ‎06-28-2018 05:34 AM by Technical Evangelist (2,428 Views)

This tutorial will show you, how you can use GeoMedia Smart Client with HTTPS.


There are two requisites necessary to do this:


  1. IIS configuration: At there is a section named IIS Manager. This will show you how to get your certificate into the IIS manager. The example there shows how you get your own certificate into IIS and use it.
  2. Also two changes have to be made in the web.config file:

Note: You will find the web.config file in your installation directory of GeoMedia Smart Client. 


      <binding name="defaultBinding">
        <security mode="Transport" />
   <serviceMetadata httpsGetEnabled="true" />



If you have finished both steps from above you should be able to go to the following URL:




Then your GeoMedia Smart Client should open up in SSL Mode. 

by Technical Evangelist
on ‎04-02-2019 03:35 AM

Some customers noticed that the client can't start because of the fact that the WSDL's still contains references to http URL's.


E.g. in case of https://YOUR_SERVER/gmsc/Authorization.svc?wsdl



<wsdl:import namespace="" location=""/>
<wsdl:types> <xsd:schema targetNamespace=""> <xsd:import schemaLocation="" namespace=""/> <xsd:import schemaLocation="" namespace=""/> <xsd:import schemaLocation="" namespace=""/> <xsd:import schemaLocation="" namespace=""/> <xsd:import schemaLocation="" namespace=""/> </xsd:schema> </wsdl:types>



This is caused by a technical limitation of WCF and happens in case of SSL-Offloading which means that the external traffic is encrypted and the internal still uses http.


Outside (https) -> [Load Balancer] -> Inside (http)


First of all, please note that the changes (basicHttpBinding and httpsGetEnabled) which were mentioned at this tutorial are not necessary in case of SSL-Offloading.


Web.config changes for SSL-Offloading:

  1. Ensure that the following header information will be forwared to the internal server:
  2. Install the URL Rewrite Module at your inside IIS -
  3. Add the following lines to the GMSC's web.config which can be found at [GMSC_INSTALL]/Program/web.config
    <urlCompression doStaticCompression="true" doDynamicCompression="false" />
    <outboundRules rewriteBeforeCache="false">
    <rule name="wsdlRewrite" preCondition="wsdlCondition" stopProcessing="true">
    <match filterByTags="None" pattern="" />
    <action type="Rewrite" value="" />
    <preCondition name="wsdlCondition">
    <add input="{HTTP_X_FORWARDED_PROTO}" pattern="^https$" />
    <add input="{RESPONSE_CONTENT_TYPE}" pattern="^text/xml" />