Registration behind Proxy Server

Article #: GEN1004Z

Product: All

Version: Released in 2012 and prior

DISCLAIMER: The content of this article may not apply to future versions of the software.

Summary:

Users are unable to register MadCap products when using a Proxy Server.

Full Description:

MadCap products fail to connect with MadCap servers during the registration process.

 

Solution:

Register by phone - contact email Customer Service

OR

If you know your Proxy settings, you can create a "config" file that will use these proxy settings while attempting to communicate with MadCaps registration servers.

Flare uses standard .NET web service calls to call the registration server.

If this call is behind a proxy, then adding an additional config file to the software installation folder should allow the software to communicate with the servers using the proxy settings.

This information was obtained from the following resources:

http://msdn.microsoft.com/en-us/library/kd3cf2ex%28VS.90%29.aspx

http://msdn.microsoft.com/en-us/library/sa91de1e%28VS.90%29.aspx

Steps to create the Config file:

  1. Open Notepad to create a config file that will be placed in the same directory where the software is installed
    1. For Flare = (C:\Program Files\MadCap Software\MadCap Flare V7\Flare.app)
    2. For Mimic = (C:\Program Files\MadCap Software\MadCap Mimic V5\Mimic.app)
  2. File Name = "Flare.exe.config" or "Mimic.exe.config" (Name if tile is based on software installed)
  3. The following should be in the "Flare.exe.config" (or config file for each product to be registered)

    <configuration>
    	<system.net>
    		<defaultProxy>
    			<proxy
    			usesystemdefault="true"
    			proxyaddress="[your proxy address and port number]"
    			bypassonlocal="false"
    			/>
    		</defaultProxy>
    	</system.net>
    </configuration>
    
  4. Save the file in the same location as the ".exe" that will use it.

When the software starts, the .NET runtime should see the config file and load the settings and apply them to any HttpRequest generated in the software.

Note: This method will not work in MadCap applications released in 2013 and beyond as this functionality has been added to the activation wizard.

Attribution:

Last updated:

February 21, 2018

Author:

Rob Hollinger

Contributions by:

Rob Hollinger