Update on Java, PHP and .NET clients.

This is a quick progress report on our work on Java, PHP and .NET clients for Grouper WS. We have decided that we will continue using Rampart 1.3 and not Rampart 1.4 as mentioned in previous postings.

This is a progress report on our work on Java, PHP and .NET clients for Grouper WS. We have decided that we will continue using Rampart 1.3 and not Rampart 1.4 as mentioned in previous postings. Although we have been exploring the usage of Rampart 1.4, however it is not as stable as we would have liked.

We had problems integrating Rampart 1.4 with WSF/PHP and we have yet to resolve these issues.Coupled with the fact that we have managed to successfuly develop .NET clients for our Rampart 1.3 enabled services mean that we don't need to incorporate Rampart 1.4 into our Grouper WS for the moment.

As mentioned above, we have successfully developed .NET clients for Rampart enabled Grouper WS. This had proved a stumbling block in the past because of timestamp validation issues. This issue was resolved after NTP synchronising the client and service machine.

So in brief, we have .NET, Java and PHP clients for both Basic Auth and Rampart enabled Grouper WS. We might explore further the integration of WSF/PHP with Rampart 1.4 in the near future but Rampart 1.3 serve our needs adequately for the moment.

Back to News