I frequently hear such things as "Are we able to load our worker info using LDAP?" Yet, the title "Lightweight Directory Access Protocol" makes me think about it as being a protocol as opposed to a physical database management system like Oracle or MSSQL.

So could someone please show me what LDAP is, what it is used, and just how it essentially works? Is LDAP just a standard protocol for removing data from a number of DBMSs? Within an architecture diagram, would LDAP be simply an arrow attracted between your DB and also the application server?

LDAP is really a protocol for querying user sites. For instance, Active Directory or Novell eDirectory both support LDAP. It's also, to some degree a syntax for doing such queries, like how SQL is really a querying language for querying databases.

An LDAP command could seem like


Also it would return all Mikes within the directory.

I believe this link states everything http://blogs.sun.com/raghuvir/entry/ldap

LDAP Is really a protocol, however, many people I understand prefer to overload its meaning to incorporate "any store able to reacting to LDAP queries." Active Directory is really an outlet, and you will find many more. It's used when designers don't worry exactly what the store is. It's utilized in just like should you say "Store it within the SQL" whenever you don't care be it MySql or Oracle or SQL Server.

LDAP is really a protocol produced in reaction towards the complexity from the X.500 group of methods. It is supposed to represent a hierarchical directory structure. The X.500 standard was initially supposed to have been used on the complete OSI layer stack and was produced to satisfy the needs from the telecom industry. LDAP was involving TCP/IP to supply similar functionality with no extra overhead. You'll find info on X.500, OSI and LDAP on wikipedia. X.500 and OSI are generally covered in many data communications books too.

Yes, LDAP (Lightweight Directory Access Protocol) is really a protocol that operates on TCP/IP.

It's accustomed to access directory services, like Microsoft's Active Directory, or Sun ONE Directory Server.

A directory services are a type of database or data store, although not always a relational database. The dwelling is generally easier, storing hierarchical collections of title-value pairs, e.g. lastName=Cruz, firstName=John.

LDAP is generally used as authentication database. Let us if you have Content management systems product you sell as Software-as-a-Service. So user will get Content management systems and also you keeping it etc.

So, you put in it to examplecustomer1.com, examplecustomer2.org, examplecustomer3.internet (one software per domain). Now you must THREE user databases to keep. Which means you add you to ultimately all systems as admin and clients accounts too.

Then you definitely uncover LDAP. You add LDAP support for your product and you have one central database of customers. You are able to login as admin to any or all systems with your personal ONE account information. Content management systems system still consists of user database and privileges for every user but username has become used as mention of the LDAP database and password area is erased from Content management systems database schema.