This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links
NISGateways
NISGateways

Version management

Difference between version and

At line 1 added 20 lines
!!! Overview
[PADL's NIS/LDAP Gateway|http://www.padl.com/Products/NISLDAPGateway.html] is a Network Information Service ([NIS]) server which sources information from LDAP, rather than flat files. With this product, enterprises can migrate organizational knowledge to LDAP whilst maintaining existing [NIS] clients.
The NIS/LDAP gateway makes a LDAP query for data on each NIS request. (There is some caching performed.)
!![NIS-to-LDAP Service|http://docs.sun.com/app/docs/doc/816-4556/6maort2tq?a=view]
The NIS–to–LDAP transition service (N2L service) replaces existing NIS daemons on the NIS master server with NIS–to–LDAP transition daemons. The N2L service also creates an NIS–to–LDAP mapping file on that server.
The mapping file specifies the mapping between NIS map entries and equivalent Directory Information Tree (DIT) entries in LDAP.
An NIS master server that has gone through this transition is referred to as an N2L server. The slave servers do not have an NISLDAPmapping file, so they continue to function in the usual manner. The slave servers periodically update their data from the N2L server as if it were a regular NIS master.
Unlike the PDAL product, the N2L is designed to read the LDAP data and then build NIS maps (like ypmake) and serve the data as NIS.
We can provide consulting and implementation expertise for the N2L Service.
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthorTop