[Pc_Support] offtopic / database schema -- COSINE/X.500 and
modern LDAP schema ...
Bryan J. Smith
b.j.smith at ieee.org
Wed Aug 16 04:25:56 EDT 2006
On Wed, 2006-08-16 at 04:16 -0400, Bryan J. Smith wrote:
> The more "modern" implementation used by most LDAP solutions today comes
> from IETF RFC2256:
> http://www.apps.ietf.org/rfc/rfc2256.html
> And a focus on the schema for an "Internet Person" in IETF RFC2798:
> http://www.apps.ietf.org/rfc/rfc2798.html
BTW, what code are you going to be setting up tables with? Accessing
via? Etc...???
There's probably already code to handle the RFC2798 schema for LDAP, so
you just need to use it for your database as well.
BTW, the YoLinux docs have an excellent table of all the attributes in
RFC2798 half-way down in its LDAP setup tutorial (yes, I found this page
via Google'ing, I'll readily admit -- but my prior response was _not_
found by just Googling -- other than the RFC2218 IWPS, didn't know about
that before) ...
http://yolinux.com/TUTORIALS/LinuxTutorialLDAP.html
inetOrgPerson object attributes:
Requires:
objectClass: organizationalPerson
objectClass: person (Inherited from object organizationalPerson)
objectClass: top (Inherited from object person)
sn (Surename/Last Name - Inherited from object person)
cn (Common Name - Inherited from object person)
May have:
o (Organization Name)
displayName (RFC2798: Preferred name of a person to be used when displaying entries)
audio
businessCategory
carLicense
departmentNumber
employeeNumber
employeeType (i.e. "Contractor", "Employee", "Intern", "Temp", "External", "Unknown", etc...)
givenName
homePhone
homePostalAddress (After street number and name use line separator "$" in LDIF file: street$ st postalCode)
initials (MS/Outlook considers this to be the middle name)
jpegPhoto (See the OpenLDAP FAQ: Turn a jpeg into ldif format)
labeledURI
mail (e-Mail address)
manager (Specify dn entry of manager)
mobile
pager
photo
roomNumber
secretary (Specify dn entry of secretary)
uid
userCertificate
x500uniqueIdentifier
preferredLanguage
userSMIMECertificate (RFC2633: A PKCS#7 [RFC2315] SignedData)
userPKCS12 (PKCS #12 [PKCS12] provides a format for exchange of personal identity information.)
Attributes inherited from object organizationalPerson:
ou (Organization unit)
title
x121Address
registeredAddress
destinationIndicator
preferredDeliveryMethod
telexNumber
teletexTerminalIdentifier
telephoneNumber (MS/Outlook considers this to be the "Business Phone")
internationaliSDNNumber
facsimileTelephoneNumber
postOfficeBox
postalAddress (MS/Outlook and Netscape both use this for the business address.)
physicalDeliveryOfficeName (MS/Outlook considers this to be the field "Office")
street (Don't use "street" because Netscape can't use it. Use "postalAddress".)
l (Locality/City/Town)
st (State/Province)
postalCode (Zip code)
Attributes inherited from object person:
userPassword
telephoneNumber (work phone)
seeAlso (URL for more info)
description
--
Bryan J. Smith Professional, technical annoyance
mailto:b.j.smith at ieee.org http://thebs413.blogspot.com
---------------------------------------------------------
The world is in need of solutions. Unfortunately, people
seem to be more interested in blindly aligning themselves
with one of only two viewponts -- an "us v. them" debate
that has nothing to do with finding an actual solution.
More information about the Pc_support
mailing list