Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have been trying to configure OpenLDAP in Ubuntu Intrepid Ibex but the guides I find in the web are confusing for me. I have had no succes.

I think the problem is most guides assume you want to use Samba for access control and use OpenLDAP as the directory for Samba. This is not what I need. I just need a central location to store client, associates, employees, family, etc. contact information and some other objects pertaining to those persons as web-sites with configuration data, their Web Sites/Databases, etc. passwords (for the Web Sites we administer for them), etc.

Do you know of any good, simple, current and clear guide available somewhere in the Web for this?

Thank you in advance.

PS: Kudos for the beta launch of SF! Congratulations to Joel, Jeff, the Team, Moderators, etc. Thank you for your support and hard work on SO and SF.

share

locked by HopelessN00b Dec 5 at 2:42

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

closed as off-topic by HopelessN00b, dawud, Katherine Villyard, Ward, Falcon Momot Feb 24 at 0:45

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions seeking product, service, or learning material recommendations are off-topic because they tend to become obsolete quickly. Instead, describe your situation and the specific problem you're trying to solve." – HopelessN00b, dawud, Katherine Villyard, Ward, Falcon Momot
If this question can be reworded to fit the rules in the help center, please edit the question.

3 Answers 3

up vote 1 down vote accepted

Been wondering about this - you are right, most of the LDAP guides focus on LDAP being used as a directory for access control.

Is there any significant reason not to store the data in a normal SQL database? you would be able to access it from anywhere meaningful, and the real reason for using a directory over a database is a directory tends to be more write-oriented, lends itself more to a hierarchical structure (non-relational data) and is easier to replicate.

Looking at the data you're wanting to store, it seems that it would be prone to updates fairly often and may be somewhat more relational than directory data (for example, linking multiple contact details to a company or website) - so a normal relational database may be more effective and easier to implement (and documentation and examples for working with it are easily available)

share
    
Hi Mark, thank you for your answer. Please see my comment to David Scmitt's. –  vmarquez May 3 '09 at 6:20
    
if you need to store specific aspects of the data in a directory (eg. contacts) then consider exporting specific parts to LDAP using LDIF. (SQL -> LDIF shouldn't be that hard). As above, the tool you should be looking at is a SQL database, not LDAP. –  Mark Regensberg May 3 '09 at 7:09
    
Thank you Mark. I will try that. I have to think on how to synchronize it both ways. –  vmarquez May 3 '09 at 9:16

Just don't. Any SQL database has better tooling than LDAP and is much easier to customize the schema to your liking.

The only reasons I would accept to using LDAP are Samba and Kerberos.

share
    
While I am already in the very early scope definition form my all-in-one tool for project planning + task management + directory + calendar + kb + information management I was expecting LDAP were the way to go as a contact + related data. SQL is a lot preffered solution for me but, then. Is there a way to integrate contact data stored in SQL with as contacts for eMail clients? Let's say: Outlook, SeaMonkey, some other? –  vmarquez May 3 '09 at 6:19
    
Ops! By the way. Thank you for your answer David :S –  vmarquez May 3 '09 at 6:19
    
Use back-sql (openldap.org/faq/data/cache/978.html) to map directly into LDAP or re-create your LDAP tree regularily by exporting the data to LDIF. You might even be able to code triggers to (manually) implement a live replication scheme. It all depends on your performance requirements. –  David Schmitt May 3 '09 at 15:23

About your project, you could use:

Microsoft Softwares: - Server Project linked to Sharepoint and Active Directory.

Linux Tools: - Alfresco softwares list.

share

Not the answer you're looking for? Browse other questions tagged or ask your own question.