Commit 0794c4b5 authored by Gavin Henry's avatar Gavin Henry
Browse files

Intro sections complete. Still some content re-working to do.

parent a4b1ba0b
......@@ -156,9 +156,41 @@ services.
H2: When should I use LDAP?
This is a very good question. In general, you should use a Directory
server when you require data to be centrally managed, stored and accessible via
standards based methods.
Some common examples found throughout the industry are, but not limited to:
* Machine Authentication
* User Authentication
* User/System Groups
* Address book
* Organization Representation
* Asset Tracking
* Telephony Information Store
* User resource management
* E-mail address lookups
* Application Configuration store
* PBX Configuration store
* etc.....
There are always new ways to use a Directory and apply LDAP principles to address
certain problems, therefore there is no simple answer to this question.
If in doubt, join the general LDAP forum for non-commercial discussions and
information relating to LDAP at:
{{URL:http://www.umich.edu/~dirsvcs/ldap/mailinglist.html}} and ask
H2: When should I not use LDAP?
When you start finding yourself bending the directory to do what you require,
maybe a redesign is needed. Or if you only require one application to use and
manipulate your data (for discussion of LDAP vs RDBMS, please read the
{{SECT:LDAP vs RDBMS}} section).
It will become obvious when LDAP is the right tool for the job.
H2: How does LDAP work?
......
......@@ -23,7 +23,7 @@ providing as much information as possible.
Note: Our Issue Tracking system is {{B:NOT}} for OpenLDAP {{B:Support}}, please join our
mailing Lists: {{URL:http://www.openldap.org/lists/}} for that
We will now attempt to discuss common user errors
We will now attempt to discuss common user errors.
H2: Checklist
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment