Easing the pain of LDAP setup

[Dax Kelson]

Getting a LDAP directory setup as a NIS replacement is needlessly
difficult. 

When setting up an LDAP directory an early first step is importing your
existing accounts. The PADL.COM scripts are included with RHL now and
are the recommend way to get your LDAP directory populated.

I wrote a single script "ldapmigrate" (free software) that replaces all
the PADL.COM scripts. The advantages of "ldapmigrate" over the PADL
scripts are as follows:

1.  My script doesn't have to run on the LDAP server itself, ie, it can
migrate /etc/* over the network.

2. It can optionally bind to the LDAP server over SSL/TLS for security.

3. It is a SINGLE ~400 line script versus the ~27 PADL.COM perl and
bourne scripts that total over 3000 lines. (see note below)

4. It is driven via command line arguments and is self documented via
--help. To use the PADL.COM scripts you must edit perl scalar variables
in various spots *inside* the scripts.

5. You can easily select the which /etc file you would like to migrate.

Finally getting to the point, I would love to have "ldapmigrate"
included in RHL to promote and encourage and ease the adoption of LDAP.
However, to do this I need the Net::LDAP module (it has a couple
dependencies) included in RHL first. Even without "ldapmigrate" the
Net::LDAP module would be a great addition.

Here is a RFE I opened in Feb 2002, please add comments if you see fit.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=59225

Dax Kelson
Guru Labs
(RHCE, Solaris, CCNP certified FWIW)

Note: I see zero point in storing certain files in your LDAP directory
such as /etc/rpc or /etc/protocols. This contributes to the reduced size
of "ldapmigrate' vs the PADL scripts.

[Ali-Reza Anghaie]

On Wednesday 23 July 2003 01:10, Dax Kelson wrote:
>  Getting a LDAP directory setup as a NIS replacement is needlessly
>  difficult.
>
>  Finally getting to the point, I would love to have "ldapmigrate"
>  included in RHL to promote and encourage and ease the adoption of LDAP.
>  However, to do this I need the Net::LDAP module (it has a couple
>  dependencies) included in RHL first. Even without "ldapmigrate" the
>  Net::LDAP module would be a great addition.
>
>  Here is a RFE I opened in Feb 2002, please add comments if you see fit.
>
>  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=59225 
Sounds interesting. Can you attach your script to the RFE as well? And any 
such documentation. It'd probably help comments and development in 
parallel.

Also consider using cpanflute2 and building your own additional RPMs for the 
Perl base and tossing them up somewhere. (Work w/ one of the major (or all) 
third-party packaging sites.)

Cheers, -Ali

-- 
OpenPGP Key: 030E44E6
--
Was I helpful?:  http://svcs.affero.net/rm.php?r=packetknife
--
Power corrupts. Absolute power is kind of neat.
-- John Lehman, Secretary of the Navy, 1981-1987

[Lucas Albers]

yes. I have bloodied myself encountering this problem.
Send me a link to your script and I will try the migration on the
redhat-beta machine as my ldap server.


The PADL scripts don't import the information correctly.
I have been hacking away at them and they are not working, correctly.
They don't generate the correct top domain.

I am in the process of migrating from NIS to ldap. I have been working on
this for a few weeks off and on.  I will continue to work on it until the
beginning of september.





I would like to setup my ldap server on the beta, because they are using
openldap 2.1.

They don't make it easy to switch to openldap.
The documentation is not adequate enough.  A number of other items need to
be installed before you can do your bidness of migrating the goods to
ldap.

>  Getting a LDAP directory setup as a NIS replacement is needlessly
>  difficult.
>
>  When setting up an LDAP directory an early first step is importing your
>  existing accounts. The PADL.COM scripts are included with RHL now and
>  are the recommend way to get your LDAP directory populated.
>
>  I wrote a single script "ldapmigrate" (free software) that replaces all
>  the PADL.COM scripts. The advantages of "ldapmigrate" over the PADL
>  scripts are as follows:
>
>  1.  My script doesn't have to run on the LDAP server itself, ie, it can
>  migrate /etc/* over the network.
>
>  2. It can optionally bind to the LDAP server over SSL/TLS for security.
>
>  3. It is a SINGLE ~400 line script versus the ~27 PADL.COM perl and
>  bourne scripts that total over 3000 lines. (see note below)
>
>  4. It is driven via command line arguments and is self documented via
>  --help. To use the PADL.COM scripts you must edit perl scalar variables
>  in various spots *inside* the scripts.
>
>  5. You can easily select the which /etc file you would like to migrate.
>
>  Finally getting to the point, I would love to have "ldapmigrate"
>  included in RHL to promote and encourage and ease the adoption of LDAP.
>  However, to do this I need the Net::LDAP module (it has a couple
>  dependencies) included in RHL first. Even without "ldapmigrate" the
>  Net::LDAP module would be a great addition.
>
>  Here is a RFE I opened in Feb 2002, please add comments if you see fit.
>
>  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=59225
>
>  Dax Kelson
>  Guru Labs
>  (RHCE, Solaris, CCNP certified FWIW)
>
>  Note: I see zero point in storing certain files in your LDAP directory
>  such as /etc/rpc or /etc/protocols. This contributes to the reduced size
>  of "ldapmigrate' vs the PADL scripts.
>
>
>  --
>  Rhl-beta-list mailing list
>  Rhl-beta-list(a)redhat.com
>  http://www.redhat.com/mailman/listinfo/rhl-beta-list
>

[Ali-Reza Anghaie]

On Wednesday 23 July 2003 01:10, Dax Kelson wrote:
>  I wrote a single script "ldapmigrate" (free software) that
> replaces all
>  the PADL.COM scripts. The advantages of "ldapmigrate" over the PADL
>  scripts are as follows:
>
>  Here is a RFE I opened in Feb 2002, please add comments if you see fit.
>
>  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=59225 
Dax, I think I'm missing something. Have you posted this 'ldapmigrate' 
script somewhere? You draw comparisons w/ PADL in the email which leads me 
to believe this is out in the wild somewhere.. I can't seem to find it.

Can you point me/us in the right direction? Where can we take a peek at this 
script of yours?

Thanks, -Ali

-- 
OpenPGP Key: 030E44E6
--
Was I helpful?:  http://svcs.affero.net/rm.php?r=packetknife
--
Umm. I'm looking for something in an after dinner burrito.
-- Homer Simpson