First thoughts on Apache Rampart 1.4 and Apache Axis 2.1.4.

We began looking into Rampart 1.4 because it supposedly provided better support for .NET clients. However, we have come across a couple of teething problems with Rampart 1.4 which might mean we have to continue working Rampart 1.3 instead.

We began looking into Rampart 1.4 because it supposedly provided better support for .NET clients. However, we have come across a couple of teething problems with Rampart 1.4 which might mean we have to continue working Rampart 1.3 instead.

Firstly, WS-Policy files are not attached to ports anymore. This means we can't use Stub classes to generate clients to invoke a service. This adds an extra layer of complexity to generating clients because generating WS clients via Stubs is probably the quickest and most efficient way of invoking a service. The workaround is to generate a client using AXIOM instead but this is a longer and more complicated process. It almost leads to generating a SOAP request by hand.

Secondly, we can't disable HTTPS for Rampart enabled services with Rampart 1.4. This is a problem because TCPMON cannot intercept encrypted SOAP messages so its impossible to do any debugging with TCPMON. This has been raised as a JIRA issue so hopefully it will be solved soon. 

Due to these problems, we might have continue with Rampart 1.3. We will also explore the easier option of deploying Grouper WS with Basic Authentication as its main secuirty mechanism. This will lead to better integration with .NET clients.

Back to News