|
Home > Archive > Unix administration > June 2004 > integrating custom NIS maps into LDAP
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
integrating custom NIS maps into LDAP
|
|
| Kevin Collins 2004-06-26, 10:10 am |
| Hi,
does anyone have any experience with migrating NIS to LDAP where custom NIS
maps are in use? I am working on a project to migrate to LDAP from NIS and we
currently have 3 custom NIS maps I have implemented and we rely on heavily for
automation.
Do I need to define my own schema for this, or is there some simpler method
available?
Thanks for any advice, examples, web-sites, etc that you can provide.
Kevin
| |
| Jonathan Abbey 2004-06-26, 10:10 am |
| In article <slrncdm5cc.nq4.spamtotrash@doom.unix-guy.com>,
Kevin Collins <spamtotrash@toomuchfiction.com> wrote:
| Hi,
|
| does anyone have any experience with migrating NIS to LDAP where custom NIS
| maps are in use? I am working on a project to migrate to LDAP from NIS and we
| currently have 3 custom NIS maps I have implemented and we rely on heavily for
| automation.
|
| Do I need to define my own schema for this, or is there some simpler method
| available?
RFC 2307 is the definitive reference on supporting NIS-style data on
LDAP. If you consult that RFC, you'll see that there is support for
an 'nisMap' object class, which can be used to represent any arbitrary
key/value mapping.
The trick isn't getting that data into LDAP, the trick is rewriting
whatever software you have that currently consults your custom NIS
maps so that it uses your unique nisMap entries in your LDAP.
Can you speak a bit about what it is that you are wanting to do?
| Thanks for any advice, examples, web-sites, etc that you can provide.
|
| Kevin
--
-------------------------------------------------------------------------------
Jonathan Abbey jonabbey@arlut.utexas.edu
Applied Research Laboratories The university of Texas at Austin
GPG Key: 71767586 at keyserver pgp.mit.edu, http://www.ganymeta.org/workkey.gpg
| |
| Kevin Collins 2004-06-26, 10:10 am |
| In article <cbg80b$2vm$1@ns3.arlut.utexas.edu>, Jonathan Abbey wrote:
> In article <slrncdm5cc.nq4.spamtotrash@doom.unix-guy.com>,
> Kevin Collins <spamtotrash@toomuchfiction.com> wrote:
>| Hi,
>|
>| does anyone have any experience with migrating NIS to LDAP where custom NIS
>| maps are in use? I am working on a project to migrate to LDAP from NIS and we
>| currently have 3 custom NIS maps I have implemented and we rely on heavily for
>| automation.
>|
>| Do I need to define my own schema for this, or is there some simpler method
>| available?
>
> RFC 2307 is the definitive reference on supporting NIS-style data on
> LDAP. If you consult that RFC, you'll see that there is support for
> an 'nisMap' object class, which can be used to represent any arbitrary
> key/value mapping.
Ok - I'll take a deeper look at the RFC...
> The trick isn't getting that data into LDAP, the trick is rewriting
> whatever software you have that currently consults your custom NIS
> maps so that it uses your unique nisMap entries in your LDAP.
This is not a problem, it is all ksh and/or PERL parsing the output, so
changing will be pretty strat forward.
> Can you speak a bit about what it is that you are wanting to do?
We are a large, highly automated SAP shop and (as one example) use a custom map
to track information relative to a specific SID: system number, SAP usage (R/3,
BW, etc), type (prod/stage/devl), default client, Oracle home dir, etc.
Currently this is a colon-delimited list, so I can probably just use the nisMap
you've already mentioned, but I was thinking it might be nice to have "named"
elements (such as "sysNumber", "sapUsage", "supType", "defaultClient", etc),
which would simplify the work our scripts are doing in parsing the list.
Kevin
|
|
|
|
|