Proxy

A Proxy (or Service Proxy) in this context is a service that has exactly the same interface as the service it shall secure. It could also be called a facade. In this security approach a Proxy is needed to enable non-intrusiveness and to handle and process service specific data. It consists of a deployable service, a proxy specific configuration file and optional additional filters. A Proxy Generator distribution can be found at the downloads page.

Generate a Proxy

Extract the archive to a folder of your choice and have a look at the release notes. Then open a shell and switch to the

${ProxyCodeGen_HOME}/bin

directory. Execute the system dependent script as follows:

  • Unices
./ProxyGen.sh -wsdl path/to/wsdl
  • Windows
.\ProxyGen.bat -wsdl path\to\wsdl

After successful generation locate the

${ProxyCodeGen_HOME}/tmp/dist

directory and find a zip file with the name of your service in it.

Proxy deployment

When your service zip is generated you can simply deploy it by unpacking its content to the ${AXIS2_HOME} folder.

NOTE: Be aware of the fact that the Proxy and the proxied service cannot run within the same Axis2 installation.

Switch to the

${AXIS2_HOME}/WEB-INF/classes

directory of the Axis2 installation where you just unpacked the zip and edit the ProxyConfiguration_${SERVICE_NAME}.xml. The configuration file already contains documentation of the single elements.

NOTE: If the net.eig.ws.pep.core.PEPManager is chosen as MessageReceiver you have to fully configure the PEP by yourself!

Regardless of what PEP is used, at least you must add a new SecuredService entry to the configuration file of the PEP in charge. Again, there is in-file- documentation present, too.