The original_import is extremely custom to our environment here but
contains many worker functions that I plan on "rolling up" into new code
at the top. Unfortunately, that code was never really meant to go
outside of our campus so it's not all that installable "out of the box".
I'll drop a README
I've hacked stuff like this together, so I also agree this would be useful.
I'm not a huge perl whiz, but I'd be happy to help with testing, etc.
On Jan 19, 2010, at 2:45 PM, Justin Alcorn wrote:
> I do much the same thing with a series of roll-your-own systems running on
> Linux. I'd love to
I do much the same thing with a series of roll-your-own systems running on
Linux. I'd love to help out.
On Tue, Jan 19, 2010 at 11:35 AM, Young, Darren <
darren.yo...@chicagobooth.edu> wrote:
> I'm in the process of creating an all Perl/LDAP based AD management set
> of libraries and scripts an
Darren,
I'd be glad to help out with a few things...
I am in a software company who is just in the process of converting several
systems to use LDAP auth via AD (not Access control just yet), and find myself
creating several scripts mostly around auditing, user support, etc.
Just a few notes:
I'm in the process of creating an all Perl/LDAP based AD management set
of libraries and scripts and am looking for any assistance in
development and/or testing it. Our overall goal has been to have a
toolset that can be used from UNIX/Linux to manage AD based objects.
Things like provisioning, dep
