AD LDAP Configuration


Overview

This guide provides information for performing LDAP operations against the UMass Amherst Active Directory (AD) instance.  The instance allows for credential binding and attribute lookup using a service account.

This service is different than the OpenLDAP service:

Many purchased applications have native AD support which should be used instead of manual configuration.

Architecture

UMass IT supports the AD LDAP connector as a service for on campus connections.  Generally client connections flow through the F5 load balancers and are forwarded to a set of AD controllers.

Hosts

Clients should use: campus-uma.umass.edu

The traffic flows through the F5 load balancer.

For TLS Connections

The address above (F5 load balancer) will not work with TLS.  Instead you must connect to the AD servers directly.  Use one of the following hosts:

Note: AD servers are replaced, and you will need to change your configuration when the AD server is replaced.

The Domain Controllers are to the F5 VIP.  In order for AD clients to function, it needs to be open to all campus IP's.  It is blocked off campus for the DC's and the VIP (the VIP is actually in 19.18).

Depending on the client software, you also have to trust the AD root certificate to use TLS.

System Accounts

System accounts must be subsidiary accounts (SUBR).  Service accounts do not require any special permissions to connect or read attributes.

Data Attributes

LDAP AttributeActive Directory AttributeLDAP vs AD DataRelease Notes
departmentNumberextensionAttribute12 Note that the department number and name are different.
displayNamedisplayNameIn LDAP this is always the full name from spire (PS_UM_SAM_ACCTVW.NAME) which looks for campus name and then primary so it isn't getting those with just a preferred name. In AD this is the Fnpref+' '+Ln if Fnpref exists, and the full name otherwise. Will always get the preferred name, and won't have access to the legal name.
eduPersonAffiliationmsExchExtensionCustomAttribute1 AD only has primary affiliation.
eduPersonPrimaryAffiliationemployeeTypeFomat and values are different between LDAP (exlample - Employee) and AD (example - PREM).The value for this attribute is represented differently in AD than in LDAP.
eduPersonPrimaryAffiliationn/a - Needed? Need another AD attribute, if possible, that has the value with the same kind of label that is in LDAP.  (See AD employeeType above.)
UMAemployeeIDemployeeID  
UMAmiddleNameinitialsLDAP contains middle name, AD contains first initial of middle name.This will just be the middle initial rather than the full middle name.
givenNamegivenNameIn LDAP this is always PS_UM_SAM_PRF_NMVW.FIRST_NAME from SPIRE and blank otherwise, but in AD this is PS_UM_SAM_PRF_NMVW.FIRST_NAME if it is set and PS_UM_SAM_ACCTVW.FIRST_NAME otherwise.This will always have a value whereas in LDAP it could have been blank.
mailmailLDAP and AD are the same. 
mailLocalAddressproxyAddressesFomat and values are different between LDAP (separate lines) and AD (list and doesn't have all aliases). Multiple addresses will be in a list rather than separate lines.  Also no all aliases will be available.
UMApreferredNamegivenNameSee entry for givenName 
snsnLDAP and AD are the same. 
uidSamAccountNameLDAP and AD are the same. 
uidn/a (uid proposed)  
UMAemailServiceextensionAttribute14  
UMAPrimaryAccountextensionAttribute15LDAP and AD are the same. 
UMAservicesmsExchExtensionCustomAttribute2 List type
UMAunionCode  Scalar type
loginShelln/a (loginShell proposed)hardcoded to /bin/bash 
homeDirectoryn/a (unixHomeDirectory proposed)  
eduPersonPrincipalNameSamAccountName Same as uid
cncnLDAP contains middle name, AD doesn't 
gecosn/a  
gidNumbern/a  
objectClassn/a  
radiusSimultaneousUse extensionAttribute9  
radiusServiceTypeextensionAttribute8  
uidNumberuidNumber UnixID, unique identifier
userPasswordn/a  
uMassEmplIDextensionAttribute13 SPIRE HR ID number
uMassGuidemployeeNumber SPIRE UITS OID ID
UMAagreementn/a  
UMAdisabledn/a  
UMAmacClassrmHomen/a  
UMAacctTypen/a  
UMOLacctn/a  
UMAstemn/a  

Search Parameters

basedn is DC=campus,DC=ads,DC=umass,DC=edu

Support

Support requests flow through ServiceNow.  Please send an email to it@umass.edu for support requests.  Please indicate that the service is AD LDAP connector.