Sneakycat CLE and LDIF Driver
Version: 0.6 beta (2012-06-07)
Use at your own risk.
What it is.
The CLE (Command Line Execute) and LDIF Driver is a simple driver that can be used to perform tasks on a Windows server using command line utilities or scripts OR import LDIF files into eDirectory.
It can be used as a subscriber only driver OR as a publisher only driver.
Subscriber only means that there is no useful functionality on the publisher channel except a driver heartbeat. You can’t use the driver to pull data into IDM, so this driver can’t replace the Novell Scripting driver.
Publisher only means that you shouldn’t use the subscriber part if you are using the publisher part. The publisher channel can be used for import LDIF files into eDirectory through IDM.
This is done by activating the LDIF Publisher channel in the Driver Configuration.
The subscriber channel is primarily intended to ease the creation of home directories on Windows servers.
It can be used by installing the Remote Loader on a Windows file server and then installing this driver there. Any commands executed by the driver will be executed on that server using the rights that the Remote Loader service has. Since the driver is written in Java it also works on Linux.
There are two publisher channels, one is a simple heartbeat that does nothing else.
Then there is the LDIF Publisher channel that reads from an LDIF file and converts the entries into DSML (Directory Services Markup Language) which is then converted to XDS using a stylesheet on the input transformation. You can remove the stylesheet (its-dsml) if you want to perform your own conversion instead or use the stylesheet from the SOAP-DSML driver instead.
What’s new in version 0.6?
CommandToExecute attribute is now supported in a <modify> event in addition
to the <add> event that was supported in the past.
What’s new in version 0.5?
Added several new pseudo attributes that can be used on the subscriber channel, read the documentation.
Added a new publisher channel that can import LDIF files and convert them to XDS for consumption by IDM.
Changed some internal code in regard to synchronization.
How much does it cost?
Nothing, it’s completely free to use but it’s not open source.
The driver only handles and events.
It will set the association value to the RDN of the object it processed. This can change in next version, I will probably make it optional.
It doesn’t handle any other events at this time (delete, rename etc.)
You could modify the driver policy to strip the association on such events and send an add with a CommandToExecute attribute to do something.
I’ll probably add support for more events in future versions.
You can send suggestions to email@example.com
If you use the LDIF publisher channel and stop the driver in the middle of processing it won’t remember where it stopped. Instead it will rename the LDIF file it was processing to .bak as if it had processed the entire file.
How it works.
The driver shim works by processing XDS documents received from the IDM engine. These documents must contain attributes that the driver understands.
In the current version it only handles <add> documents.
There is an attribute called CommandToExecute that can be used to execute any command line or script that you want.
There are several others attributes that must be used together to have any effect.
For usage information read the PDF that comes with the driver.
There is no real support but you can send me e-mail at firstname.lastname@example.org and I’ll try to respond.
You can also send suggestions to the same address.
I TAKE NO RESPONSIBILITY IF YOU MESS SOMETHING UP BY USING THIS DRIVER. Please read LICENSE.txt before using this.