Overview#Our objective is to show how the SOAP driver could be utilized. The concepts resented here are based on a real-life production system.
We have seen a lot of questions about the SOAP driver and many people either understand Driver, but not SOAP or people understand SOAP and not Drivers.
Our attempt to marry the two with a rather simple application interface that will send SOAP-DSML requests to the driver and evaluate the responses form the driver.
Items To Note about the System#In this particular case, we only operate from the SOAP-DSML Client to the SOAP-DSML Driver. Although the SOAP-DSML Driver is capable of initiating requests on changes in the IDV, it was not required or desired for our implementation.
The SOAP-DSML Client can not be queried and can only receive responses from the driver as a result of a request. Although our implementation only deals with user entries, the concepts hold true.
The base purpose of implementation was to:
- Allow other applications to utilize SOAP services to perform some functions to the IDV that were not able (or willing) to utilize a driver for connection.
- Many of the application developers had little or no knowledge of LDAP or NDS. So the application was made to be simple yet flexible.
Security#We did implement security between the driver and the application. It is not done here as it is specific to each environment. We strongly recommend that you implement security that is appropriate to your environment.
- Details on the SOAP-DSML Driver - SOAP DSML Driver And Application/SOAP-DSMLDriver.xml
- Details on the SOAP-DSML Client - SOAP DSML Driver And Application/SOAPDSMLClient.zip