Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

How would you design this LDAP schema

Posted on 2007-12-04
3
Medium Priority
?
989 Views
Last Modified: 2013-12-24
We are looking at building a ldap directory for mail servers.

We are looking at building something similar to what I have below.  I am looking for an idea on how the schema would be designed (LDIF format is fine).

We would have multiple companies (customers) each with 1 more more domain names.  Under the domain name would be 1 or more email addresses (primary and 0+ aliases).  

So we may have 50 companies with one or two domain names with 15-150 users under each domain name and 1 primary email address with 0 - 10 secondary email addresses.  We want to be able to query at the top of the tree for an email address (when querying, we do not care what company it belongs to and what domain name, we will simply look in the directory to see if the email address exists).

Is it possible to put UID's in groups by domain and company like this and still search for "UID->Email" accross all groups?

What would the schema look like to handle this?

Top of Tree (Our dc;dc?)
     Company (Customer) name
          Domain Name 1
                  User ID 1
                      primary email address
                      alias 1
                      alias 2
                      alias 3
                      ...
                  User ID 2
                      primary email address
                      alias 1
                      alias 2
                      alias 3
                      ...
                  User ID 3
                      primary email address
                      alias 1
                      alias 2
                      alias 3
                      ...
          Domain 2
          ...
                  ...
0
Comment
Question by:CharlieBeBop
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 27

Accepted Solution

by:
Nopius earned 2000 total points
ID: 20469540
You don't need to implement a _schema_. Standard objectClasses and attributes may be used for your LDAP tree.

One problem with aliases. Alias is typically defines a group of email addresses withing domain, it is not an attribute of the user. Of course you _can_ treat is as one more email address for each user, but you will have problems when someone removes or modifies alias in their domain name.

Another problem, when a customer owns 2+ domain names and user 'smith' is the same user in all domains, what is primary email then (when letter to smith@domain1.com and smith@domain2.com goes to the same mailbox not being an alias of each other)?

What would you use an UserID? Email address? Unique letters+number combination?

> Is it possible to put UID's in groups by domain and company like this and still search for "UID->Email" accross all groups?

Regardless of uniqueness of UID and your schema, you can perform such searches.

You may use inetOrgPerson as a STRUCTURAL oblectclass for the user and and inetMailRouting as an AUXILARY object class (it's definition can be found here: http://grotan.com/ldap/mail.schema)

As a primary mail attribute you may use 'mail', as aliases - 'rfc822MailAlias'.

To perform search by UID, perform use a subtree 'sub' scope, "(uid=your_id)"  (if you choose 'uid' as an UID attribute) and mail rfc822MailAlias as an output attributes.

But before implementing, I recommend you read more LDAP related materials, starting from:
http://en.wikipedia.org/wiki/LDAP
http://en.wikipedia.org/wiki/LDIF

0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Microsoft Access is a place to store data within tables and represent this stored data using multiple database objects such as in form of macros, forms, reports, etc. After a MS Access database is created there is need to improve the performance and…
This article shows how to get a list of available printers for display in a drop-down list, and then to use the selected printer to print an Access report or a Word document filled with Access data, using different syntax as needed for working with …
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question