The objective is to show how the SOAP driver could be utilized. The concepts presented here are based on a real-life production system. I used the Novell Identity Manager with an instance of the SOAP Driver to create a system that would use SOAP to allow user creations, modifications, searches and deletions.
I have seen a lot of questions about the SOAP driver, and many people either understand the driver but not SOAP, or people understand SOAP and not drivers.
My attempt is to marry the two with a rather simple application interface that will send SOAP-DSML requests to the driver and evaluate the responses from the driver.
The driver is a straightforward implementation of the SOAP Driver, with a few style sheet changes and some normal "business" logic applied.
The purpose of the SOAP-DSML Client is to write properly formatted SOAP-DSML packets that can be consumed by SOAP-DSML Driver. However, I believe that the SOAP-DSML Client would be capable of communicating with nearly any SOAP-DSML application, keeping mind the limitations that are noted.
This client is written in Java and requires at least Java 1.5 for operation. The Client makes use of the Open Source JLDAP Java libraries.
Generally, the SOAP-DSML Client is agnostic to attributes and values that are provided. The Attribute Names and attribute values will be passed to the SOAP-DSML Driver as provided.
The Driver configuration and client, and even more information, are available from:
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.