Skip Navigation
NACS > Telephone Services > New LDAP Directory Information

New LDAP Directory Information

A guide to the new Schema for LDAP users

Summary: LDAP usage information and notes about the change to the field names for directory information in LDAP in order to comply with internet naming standards.

IMPORTANT: The LDAP schema has changed. Any automated clients querying LDAP must be updated to use the new schema! See the table below for schema translations.

General LDAP Information

URL

The current LDAP URL is ldap://ldap.service.uci.edu or ldap://ucildapv3.service.uci.edu.

Base DN

"ou=University of California Irvine,o=University of California, c=US" -- this has not changed in the new version.

DN of a ucinetid

"uid=XXXXXXX,ou=University of California Irvine,o=University of California, c=US" where XXXXXXX = the ucinetid of the object -- this has not changed in the new version.

Using TLS (Transaction Layer Security)

The new version of LDAP supports TLS. LDAP using SSL (ldaps) is not supported. In order to use TLS, the client must connect to the ldap server on the unsecure port 389 and issue the command startTLS. Security will then be negotiated. Most LDAP clients support this. The certificate is self signed, and can be authenticated with the Certificate Authority cert found here: Certificate. The certificate will change once the system is renamed to ldap.service.uci.edu. Some clients may require the certificate.

Private Data

The data in UCI's ldap directory is separated into public and private zones. Normal users cannot get access to the private data, which holds information such as birthday and student ID. If you would like to apply for access to private information, email nacs@uci.edu.

Roles and Affiliations

Currently, a directory entry's affiliation with UCI is in the uciAffiliation attribute. This is a multi-valued attribute, so an entry could have two or more affiliations. For example, if a person was both a student and staff, they would have the 'student','employee' and 'staff' affiliation (staff as opposed to faculty). The current affiliations are: student, employee, staff, faculty, guest, retiree, group, and former_student.

Attribute Names in PH, Old LDAP Service, and New LDAP Service

The following table shows the current PH (UCI Directory) schema on the left, and the LDAP schemas on the right. The table also shows which PH fields in LDAP will be publicly viewable. The newest version of LDAP has been designed so that all of the PH data will be in LDAP. Some names and formats have also changed with the new schema. These changes have taken place in an attempt to make our LDAP directory more standards compliant. See below for a color key and more notes on changes.

PH Field NameOld LDAP NameNew LDAP Field Name(s)AliasesPublicFormat Changes
activated_onactivatedOnX
adddateaddDate
aliasuid,ucinetid,sn,eduPersonPrincipalNameuid,ucinetid,eduPersonPrincipalNameX
answeranswer
b_daybDaybDay in dateTime format
callsigncallsignX
campus_idcampusIdcampusIdX
curriculumcurriculumX
delete_datedeleteDateX
departmentdepartmentdepartmentX
department_codedepCodedepartmentNumberdepCodeX
department_code2depCodedepartmentNumberdepCodeX
department2departmentdepartmentX
dept_phonedeptPhoneX
emailmailForwardingAddressmailDeliveryPointmailForwardingAddressX
email_addressmailmailX
emailnameemailNameX
employee_idemployeeIdemployeeNumberemployeeId
emptimeempTime
extextextX
fax_numberfax-numberfacsimileTelephoneNumberfax,fax-number,faxNumberXfacsimileTelephoneNumber in phone format
flagsflags
guest_expirationguestExpirationXguestExpiration in dateTime format
guest_idguestIdguestId
guest_reasonguestReasonX
guest_sponsorguestSponsorX
heroheroX
home_addresshomePostalAddress,streetstreetAddress
home_cityllocalityName
home_page_urlhome-page-urlhomePageUrlhome-page-urlX
home_phonehomePhonehomeTelephoneNumber
home_statest
home_ziphomeZip
hourshoursX
idaltId
last_first_namesn,lastFirstNameXsn only has last name
N / AlastRefreshXlast refresh of data in record in ldap
lastresetlastResetXlastReset in dateTime format
lkalkaX
mail_addressmailAddress
mailcodemailcodepostalCode,mailcodeXpostalCode has 92697 added
majormajormajorX
namecn,givenName,sndisplayName,cn,givenName,snXgivenName only has first name
nicknamecncn,nickNameX
office_addressaddresspostalAddressX
office_address2addresspostalAddressX
other_infootherInfoX
payroll_titlepayrollTitle
phonetelephoneNumbertelephoneNumberphoneXstandard phone number format
picture_urlpicture-urlpictureUrlpicture-urlX
printedprintedX
projectprojectX
questionquestion
receive_printedreceivePrintedX
release_personalreleasePersonalreleasePersonalX
rewriterewriteX
searchnamesearchName
stu_email_releasestuEmailReleasestuEmailRelease
student_addressstudentAddressX
student_idstudentIdstudentId
student_id2studentId
student_levelstudentLevelX
student_phonestudentPhoneXstudentPhone in phone number format
summer_idstudentId
titletitletitleX
title2titletitleX
typeeduPersonAffiliation,uciAffiliationuserClass,type,eduPersonAffiliation,uciAffiliationX
UCSAucsaX
udir_iducnetiducnetId
unex_idstudentId
lastRefreshXlast refresh of data in the ldap record
methodOfIssuanceXmethod id was issued
levelOfAssuranceX1-5 scale of how straong authentication is
suspectXflag for suspected duplicate identities
titleCodeprimary payroll title code
facultyLevelXFull,Associate or Assistant if primary title code is faculty
facultyLevelXFull,Associate or Assistant if primary title code is faculty
phhashMD5 hash of ph record, useful for detecting changes to PH data

Color Key
No Changes to schema since previous LDAP version
Changes Made
New PH field in LDAP

A Note on LDAP Aliases

A number of aliases for attributes have been incorporated into the schema for legacy support.

If your application specifies attribute names to be returned, the alias system will understand the attribute you are requesting, and return attributes those attributes, however, they will be named with their primary names in the return result.

If, however, your queries does not specify which attributes it wants returned, the attribute names returned will be their new official names. One can also use aliased names in search filters.

For example, the PH field 'phone' is now stored in LDAP as 'telephoneNumber' in accordance with the iNetOrgPerson schema. 'phone' is also now an alias for 'telephoneNumber'. If the attribute 'phone' is requested, the attribute will show up in the response as name 'telephoneNumber'. If a general query of all data occurs without specifying attribute names, the attribute will be returned as 'telephoneNumber'.

Note regarding case sensitivity

While LDAP is not case sensitive, many programming language are. Any query being made to the LDAP server will be case insensitive. However, once an ldap result is being used inside a case sensitive programming language, the language will treat attribute names as case sensitive. This is the case in PHP. PHP will automatically lowercase all attribute names in a result hash to avoid confusion.

Schema Information

Object Classes

NameOIDNotes
uciperson2.16.840.1.113916.5.6.2.1used for PH type guest, student and person (staff/faculty) -- inherits from iNetOrgPerson and is supplemented by eduPerson
uciobject2.16.840.1.113916.5.6.2.2structural object, used for inheritance only
uciforward2.16.840.1.113916.5.6.2.3used for PH type forward or duplicate
ucimaillist2.16.840.1.113916.5.6.2.4used for PH type list
ucigroup2.16.840.1.113916.5.6.2.5used for PH type group
ucidepartment2.16.840.1.113916.5.6.2.6used for PH type dept
ucinetreg2.16.840.1.113916.5.6.2.7used for PH type netreg

UCI Custom Attributes

NameOIDData TypeSingle or Multi ValuedIndexed in Database?
activatedOn2.16.840.1.113916.5.6.1.15stringSINGLE-VALUE
addDate2.16.840.1.113916.5.6.1.16stringSINGLE-VALUE
altId2.16.840.1.113916.5.6.1.49string
answer2.16.840.1.113916.5.6.1.17stringSINGLE-VALUE
bDay2.16.840.1.113916.5.6.1.18date and timeSINGLE-VALUE
callsign2.16.840.1.113916.5.6.1.22string
campusId2.16.840.1.113916.5.6.1.8stringSINGLE-VALUEindexed
curriculum2.16.840.1.113916.5.6.1.19stringSINGLE-VALUE
deleteDate2.16.840.1.113916.5.6.1.20stringSINGLE-VALUE
department2.16.840.1.113916.5.6.1.2stringindexed
deptPhone2.16.840.1.113916.5.6.1.21string
emailName2.16.840.1.113916.5.6.1.55stringSINGLE-VALUEindexed
empTime2.16.840.1.113916.5.6.1.23string
ext2.16.840.1.113916.5.6.1.11stringindexed
facultyLevel2.16.840.1.113916.5.6.1.57stringSINGLE-VALUE
flags2.16.840.1.113916.5.6.1.24string
guestExpiration2.16.840.1.113916.5.6.1.25date and timeSINGLE-VALUE
guestId2.16.840.1.113916.5.6.1.5stringSINGLE-VALUEindexed
guestReason2.16.840.1.113916.5.6.1.26string
guestSponsor2.16.840.1.113916.5.6.1.27string
hero2.16.840.1.113916.5.6.1.28stringSINGLE-VALUE
homePageUrl2.16.840.1.113916.5.6.1.12string
homeZip2.16.840.1.113916.5.6.1.29stringSINGLE-VALUE
hours2.16.840.1.113916.5.6.1.30string
lastFirstName2.16.840.1.113916.5.6.1.31stringindexed
lastRefresh2.16.840.1.113916.5.6.1.51date and timeSINGLE-VALUE
lastReset2.16.840.1.113916.5.6.1.32date and timeSINGLE-VALUE
levelOfAssurance2.16.840.1.113916.5.6.1.53stringSINGLE-VALUE
lka2.16.840.1.113916.5.6.1.33string
mailAddress2.16.840.1.113916.5.6.1.34string
mailcode2.16.840.1.113916.5.6.1.10stringSINGLE-VALUE
mailDeliveryPoint2.16.840.1.113916.5.6.1.6stringSINGLE-VALUE
major2.16.840.1.113916.5.6.1.4string
methodOfIssuance2.16.840.1.113916.5.6.1.52stringSINGLE-VALUE
nickName2.16.840.1.113916.5.6.1.50string
otherInfo2.16.840.1.113916.5.6.1.35string
payrollTitle2.16.840.1.113916.5.6.1.36string
phhash2.16.840.1.113916.5.6.1.58string
pictureUrl2.16.840.1.113916.5.6.1.7string
printed2.16.840.1.113916.5.6.1.37stringSINGLE-VALUE
project2.16.840.1.113916.5.6.1.38string
question2.16.840.1.113916.5.6.1.39stringSINGLE-VALUE
receivePrinted2.16.840.1.113916.5.6.1.40stringSINGLE-VALUE
releasePersonal2.16.840.1.113916.5.6.1.13stringSINGLE-VALUEindexed
rewrite2.16.840.1.113916.5.6.1.41stringSINGLE-VALUE
searchName2.16.840.1.113916.5.6.1.42stringindexed
socialSecurity2.16.840.1.113916.5.6.1.43stringSINGLE-VALUEindexed
studentAddress2.16.840.1.113916.5.6.1.44stringSINGLE-VALUE
studentId2.16.840.1.113916.5.6.1.3stringindexed
studentLevel2.16.840.1.113916.5.6.1.45stringSINGLE-VALUE
studentPhone2.16.840.1.113916.5.6.1.46telephone numberSINGLE-VALUE
stuEmailRelease2.16.840.1.113916.5.6.1.14stringSINGLE-VALUEindexed
suspect2.16.840.1.113916.5.6.1.54stringSINGLE-VALUE
titleCode2.16.840.1.113916.5.6.1.56string
type2.16.840.1.113916.5.6.1.48stringSINGLE-VALUEindexed
ucinetid2.16.840.1.113916.5.6.1.1stringSINGLE-VALUEindexed
ucnetId2.16.840.1.113916.5.6.1.9stringSINGLE-VALUEindexed
ucsa2.16.840.1.113916.5.6.1.47stringSINGLE-VALUE
uciAffiliation2.16.840.1.113916.5.6.1.59stringindexed

Standard Attributes used in UCI's Directory

UCI also uses a number of attributes from other schemas, most notably iNetOrgPerson (and all of its inherited schema), and eduPerson.

Attribute NameAliasRFC Spec. NumberIndexed in Database?
cncommonName2256indexed
departmentNumber2798indexed
displayName2798
employeeNumber2798indexed
facsimileTelephoneNumberfax2256
givenNamegn2256indexed
homePhonehomeTelephoneNumber1274
homePostalAddress1274
llocalityName2256
mailrfc822Mailbox1274indexed
postalAddress2256
postalCode2256
snsurname2256indexed
ststateOrProvinceName2256
streetstreetAddress2256
telephoneNumber2256indexed
title2256
uiduserid1274indexed
userClass1274indexed
userPassword2256 2307