Connecting to Galileo Web Services through a Secured Firewall

Most Web Services toolkits are not currently designed to support Web Service proxy classes that make calls through secured firewalls via a proxy server. Authentication errors typically result because the proxy server does not receive the necessary security credentials to allow the data to pass though the firewall.

There are several possible solutions to support Galileo Web Services calls through a secured firewall, depending on the platform or toolkit:

• In .NET, a new proxy object can be created to include the authentication credentials required to access Galileo Web Services via the proxy server. This proxy class is then sent with each call to Galileo Web Services.

• In Apache SOAP, a properties object that contains the proxy server credentials can be sent with each call to Galileo Web Services.

• In Apache Axis, the system properties can be configured at an application level to support a proxy server, so that the proxy server credentials do not need to be explicitly included in each call to Galileo Web Services.

• In either platform, the proxy authentication process can be bypassed by excluding the Galileo IP address from the browser connection properties, and creating a static route directly from the local machine to the Galileo IP address. However, this method may create maintenance issues, and is not typically recommended for Galileo Web Services.