Changes between Version 15 and Version 16 of Phase1Planning
- Timestamp:
- 07/27/12 14:36:19 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Phase1Planning
v15 v16 27 27 ''UID is opaque and unique to LDAP; standard unique identifiers are UA Username in UASystemID in LDAP which is name based but may change as names change; and UA ID# or BannerID in LDAP which unchanging numeric ID.''[[br]]Use UA subject ID = ID#, BannerID, typically an 8-digit numeric. 28 28 29 ''I've met with the statewide AD admin 2012-07-27 and based on his input I'm proposing we use AD as the subject source; we'll search the Enterprise LDAP directory for buildings to create groups based on those users. AD has many more users because it initially loaded the entire history of UA people from our ERP. However, only recent people have uaIdentifier - the unique assigned generally numeric id. I assume that the existence of many records without the key (uaIdentifier) in AD will not interfere with Grouper operations. If people do a name based search, those without that key should be ignored (for example, by including a (uaIdentifier=*) clause in the search .29 ''I've met with the statewide AD admin 2012-07-27 and based on his input I'm proposing we use AD as the subject source; we'll search the Enterprise LDAP directory for buildings to create groups based on those users. AD has many more users because it initially loaded the entire history of UA people from our ERP. However, only recent people have uaIdentifier - the unique assigned generally numeric id. I assume that the existence of many records without the key (uaIdentifier) in AD will not interfere with Grouper operations. If people do a name based search, those without that key should be ignored (for example, by including a (uaIdentifier=*) clause in the search). 30 30 31 That attribute - uaIdentifier in AD == BannerID in LDAP may be used as the index .31 That attribute - uaIdentifier in AD == BannerID in LDAP may be used as the index or Subject ID in Grouper. 32 32 33 33 * What attribute will have the users' names? Assuming displayName for now.[[br]]
