SOAP UDDI: Developing infrastructure software for web-services

The goal of this project is to develop all the missing pieces that currently exist in deploying an enterprise-level application over web-services platform. This project is sponsored by Induslogic, Inc. which is building a full-fledged commercial implementation of web-services in its Xintegrate range of products.



Implementation of UDDI 2.0 compliant registry

We have developed a UDDI 2.0 compliant registry for Web services in a private intranet environment. This is a reference implementation of UDDI  specification. With this UDDI Registry, Web services developers can publish and test their applications in a secure, private environment for their own applications. The Project can be useful to all those who want to make their own uddi registry. Even if you just want to make UDDI clients and are tired of connecting to the IBM or Microsoft registries over the net for testing, you may want to have a local registry.

Current Features:

  • Ready for deployment in private intranet environments.
  • Conforms to UDDI 2.0 specifications.
  • Written completely in JAVA.
  • Persistence at the back-end using relational databases. Current release supports MS-Access, MS-SQL Server, Postgres and Sybase.

This registry is geared toward activities such as Web services development, testing, and deployment for internal applications, and therefore it has different requirements and characteristics than public UDDI registries. In particular, it does not currently allows replication or data exchange with other registries. We hope to add this functionality in future depending on what you guys demand (and are ready to help out on !!)

Planned Features:

  • Replication support with other registries to allow working as a public repository.
  • Synchronization to support multiple instances and provide robustness.
  • Support for LDAP infrastructure at the backend.

Apache module to authorize user SOAP requests on per service or per method basis

This package allows you to authorize your SOAP clients on per-service or per-method basis. The control is currently based on either XML Signatures (dependant on external XML Signature library) or  user/password based which has to come embedded in the HTTP header. While the actual job of authentication and authorization is still handled by mod_auth (or your favorite Apache authentication module), this layer adds intelligence to do this at SOAP service and method level instead of at the URL level.

 To know how it works click here.

Current Features:

  • Authentication using private key XML signatures.
  • Provides access to service and methods based on user. 

Planned Features:

  • Removal of dependency on external XML Signature Library (due on Dec 7)
  • Support for XML Encryption (due on Dec 14).
  • Conversion to pure servlet to remove dependency on Apache
  • Conversion to pure Apache Module to remove dependency on Java
  • Support for IP and machine based restrictions
  • Distributed Authentication Support
  • Support for P3P



Tarun Upadhyay - lead for project - works for Induslogic Inc. More information about him could be found at his personal web-site at


SourceForge Logo