Like with NIS, you can provide and serve a wide variety of data through LDAP, and it has become something of a standard with medium sized and larger organisations. LDAP is a protocol that many different directory services and access management solutions can understand.

Apache is a web server that uses the HTTP protocol. ... DNS, NIS and LDAP. LDAP VS NIS LDAP versus NIS. NIS is (Network Information Services) A naming service from Sun that allows resources to be easily added, deleted or relocated. Active Directory. Below is a quick comparison between FNS, DNS, NIS, NIS+ and LDAP naming services. It also seems that the more I search to more people are using LDAP and documenting this while use of NIS is non-exsistant. lightweight directory access protocol LDAP organises data into a hierarchy, allowing it to be administered based on company, branch, department or any other method you choose.

The nscd is a daemon that provides a cache for the most common name service requests like passwd, group, hosts, service and netgroup.. sssd primarily provides daemons to manage access to remote directories and authentication mechanisms like LDAP, Kerberos, NIS, etc...so it is more about authentication and authorization. I am currently running a project to setup ldap authentication and access control for Solaris/Linux/Windows, webservers, radius server, proxy server, etc as well as storing all address book type information using openldap. NIS Maps And LDAP Attributes # A reference to NIS Maps And LDAP Attributes LDAP Schemas For NIS In LDAP # LDAP Schemas For NIS entries In LDAP NIS Limitations # NIS Limitations and if they will be present when you are using LDAP.

Unlike NIS, the LDAP service is not restricted to pure Unix networks. The Lightweight Directory Access Protocol was designed as a way to access directories containing all matter of information. There are advantages in integrating *NIX accounts within LDAP, which you may think brings new complications, but it is more like putting your NIS structure within LDAP. Or possibly make the AD Server a slave to the NIS/LDAP Server. As for Red Hat Directory Server: I actually never noticed that HP had bundled this in HP-UX since a while, I thought it was a third party product.

LDAP support is implemented in Web browsers and e-mail programs, which can query an LDAP-compliant directory.

Overall NIS is simple to use and configure, but there are some inherent short comings in its inability to control security policies. What we learned about LDAP schema used by autofs # Worried about NIS Performance vs. LDAP? LDAP Naming Service Versus Other Naming Services. I want all the user account in the Master Server. Luis, There is no need to run ldap and NIS together unless you want to do automounting for Unix systems. for users and groups … While LDAP information is fairly easy to find and understand I am still looking for good NIS Documentation. Windows servers (from 2000) support LDAP as a … NIS is only designed for Unix platforms, and is not suitable as a centralized data administration tool in heterogeneous networks.

It didn't take long for someone to consider storing UNIX information in a directory and using LDAP to access it. It does have its own caching mechanism e.g.

Re: NIS vs. LDAP Indeed administring an LDAP server does not seem trivial, but enduring a SOX audit with a basic NIS server would scare the hell out of me!

LDAP vs. The relationship between AD and LDAP is much like the relationship between Apache and HTTP: HTTP is a web protocol. LDAP is a way of speaking to Active Directory. LDAP is a sibling protocol to HTTP and FTP and uses the ldap:// prefix in its URL.