Changes between Version 3 and Version 4 of Phase1Planning
- Timestamp:
- 07/09/12 11:42:47 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Phase1Planning
v3 v4 27 27 ''displayName in LDAP, but cn in AD; cn is multi-valued in LDAP'' 28 28 - LDAP searches will be based on the uid and displayName attributes. 29 ''Why displayName? UID is opaque and not generally suitable except in two-step process (1) search on name, or known unique identifier to obtain dn , then (2) query for desired attributes in that dn.''29 ''Why displayName? UID is opaque and not generally suitable except in two-step process (1) search on name, or known unique identifier to obtain dn (like "uid=12wynpgyz01,ou=people,dc=alaska,dc=edu"), then (2) query for desired attributes in that dn.'' 30 30 - Subject sorting will be based on the displayName attribute. 31 31 ''displayName is '!PreferredFirstName sn'; perhaps sort on sn?''