Use the following procedure to convert the Developer server from a non-secure to a secure server.

To convert the Developer server from non-SSL to SSL:

1. Install and run the Developer server on a non-SSL web site.
    
2. Log in to the Developer and create a Profile, using the HTTP bound web site URL for the Library Location.
    
3. Exit the Developer.
    
4. Apply the certificate and HTTPS bindings to the web site on which the Developer server is installed.
    
5. Navigate to the installation location and open the Repository.WCF\web.config file in the editor of your choice.
    
6. Locate the XML value for the node configuration/system.serviceModel/bindings/basicHttpBinding/binding. There should only be one "name" attribute.
    
7. Locate the “security” key located within the key and change the "mode" attribute from “None” or "TransportCredentialOnly" to "Transport".
    
8. Locate the XML value for the node configuration/system.serviceModel/bindings/customBinding/binding/upkHttpsTransport. There should only be one node with this name.
    
9. Rename the node from upkHttpsTransport to httpsTransport.
    
10. Save the changes and close the web.config file.
     
11. Log in to the Developer using the Profile with the original non-SSL Library Location. If the HTTP binding has been removed from the site, you can open the Profile as Disconnected.
     
12. On the Tools menu, choose Profiles.
     
13. If you are in the profile that is on the affected web site, click Exit Profile, then select the profile to modify and click Edit.
     
14. In the Profile wizard, edit the Library Location URL to point to the new SSL location.
     
15. Log in to the Developer and verify it works.

Table of Contents  Back