Problems with Grouper WS 1.3.0

Rampart authentication not working in Grouper WS 1.3.0

The official Grouper WS 1.3.0 has been released but we are having problems getting Rampart authentication to work.

The official Grouper WS 1.3.0 has been released but we are having problems getting Rampart authentication to work. It appears that Axis2 doesn't like it when 2 services use the same business class, which is currently the case with Grouper WS 1.3.0.

After speaking to Chris Hyzer, we came to the conclusion that the only fix (at the moment) is to have 2 separate web apps, one for basic auth and another for WS-security authentication (via Rampart). The choice of authentication technique would be made at build time. Although this is a rather inelegant solution, it is probably the best solution for now. Future developments will look at a more elegant approach that will enable all 3 Webservice types to be deployed and used at the same time, those being SOAP + basic auth, SOAP + WS-security (via Rampart) and REST.

Users can decide to use either basic auth or WS-security authentication (via Rampart) as their security mechanism. Newcastle University plans to use WS-security authentication (via Rampart) as our security mechanism because many of the other platforms in use within Newcastle are compliant with the WS-security stack. I particlar web applications developed in .NET via visual studio and the SAP webservice stack are drivers for creating WS-Security aware webservices.

Back to News