Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id BAD80200BFC for ; Sat, 31 Dec 2016 04:13:09 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id B985A160B3F; Sat, 31 Dec 2016 03:13:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0E21A160B32 for ; Sat, 31 Dec 2016 04:13:08 +0100 (CET) Received: (qmail 22964 invoked by uid 500); 31 Dec 2016 03:13:08 -0000 Mailing-List: contact commits-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@directory.apache.org Delivered-To: mailing list commits@directory.apache.org Received: (qmail 22955 invoked by uid 99); 31 Dec 2016 03:13:08 -0000 Received: from Unknown (HELO svn01-us-west.apache.org) (209.188.14.144) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 Dec 2016 03:13:08 +0000 Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id 877433A022C for ; Sat, 31 Dec 2016 03:13:07 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1003810 - in /websites/staging/directory/trunk/content: ./ api/user-guide/1.2-ldap-in-a-few-words.html Date: Sat, 31 Dec 2016 03:13:07 -0000 To: commits@directory.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20161231031307.877433A022C@svn01-us-west.apache.org> archived-at: Sat, 31 Dec 2016 03:13:09 -0000 Author: buildbot Date: Sat Dec 31 03:13:07 2016 New Revision: 1003810 Log: Staging update by buildbot for directory Modified: websites/staging/directory/trunk/content/ (props changed) websites/staging/directory/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.html Propchange: websites/staging/directory/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Sat Dec 31 03:13:07 2016 @@ -1 +1 @@ -1776680 +1776681 Modified: websites/staging/directory/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.html ============================================================================== --- websites/staging/directory/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.html (original) +++ websites/staging/directory/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.html Sat Dec 31 03:13:07 2016 @@ -185,18 +185,18 @@ h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }

1.2 - LDAP in a few words¶

LDAP is not a new technlology. It has been around since the 90's to mitigate complexities inherent in X.500 usage. Its name refers to Lightweight Directory Access Protocol. Soon after the first standard was issued, the first full LDAP server was created and X.500 became obsolete.

We'll use the term LDAP to represent the protocol and LDAP server to represent the server that implements it.

We'll use the term LDAP to represent the protocol and LDAP server to represent the server that implements it.

Features¶

The LDAP protocol provides access to entries stored in a LDAP Server's database. It provides the mechanism for fast searching and retrieval of entries. Its data structures are hierarchical, and uses a schema to manage the definition of a particular entry's data formats.

An LDAP client must first connect to a server and disconnect when finished. Some operations may be performed on the data itself, e.g. searches, modifications and deletions, along with a few others.

LDAP servers are extensible, but they all use a common protocol which makes it easy for users to request to interact with them, in a way that isn't tied to a particular vendor's implementation. This API is an example of what LDAP is good at: fast data access across servers of all types.

LDAP servers are extensible, but they all use a common protocol simplifies application access in a way that isn't tied to a particular vendor's implementation. This API is an example of what LDAP is good at: fast data access across servers of all types.

Characteristics¶

LDAP servers are fast for retrievals, having been designed specifically for this purpose. But modifications can be costly. These characteristics must be understood when writing applications that use an LDAP server for data storage.

Each entry is associated with a location within its corresponding Directory Information Tree, and we use what is known as a Distinguished Name (or Dn) to describe this address. The base entry is known as the suffix, it along with all entries beneath it are collectively known as the DIT.

Each entry is associated with a location within its corresponding Directory Information Tree, and we use what is known as a Distinguished Name (or Dn) to describe this address. The base entry is known as the suffix. The suffix along with all entries beneath it are collectively known as the DIT.

Programming¶

LDAP is a part of the IT landscape and so it's necessary to learn how to deal with it. LDAP servers are used to manage authentications, authorizations, demographic information about users and more. It's very likely that you will have to write some code to access data with LDAP at some point, and existing APIs aren't quite up to the task. This LDAP API has been designed to simplify usage and ensure proper interaction with the server.

Going further¶

This was a very short introduction, there's more literature about LDAP on the web : Wikipedia provides a good starting point.

This was a short introduction, there's more literature about LDAP on the web : Wikipedia provides a good starting point.