Body
This is a Spring Boot application that will be in-place on iamscripts1.sys.oakland.edu (/opt/ou/iamscripts/bannerattributesync). It will be CRONNED to run nightly (and is the replacement for StartLdapSync.
Who is Eligible?
Active Faculty or Staff
Description
Banner Attribute Sync is a replacement for StartLdapSync. It takes Banner data ("Who should have this attribute?") and compares it to who has the Attributes in LDAP. It then identifies any Attributes that need to be updated in LDAP, added OR removed, and updates them. Finally, it logs the updates in IAMDB in the events and event_info tables.
This application uses BannerApi, LdapApi and PostgresApi.
Synchronized Data
The data used for the synchronization process originates in Banner. There is one query per Attribute used to identify who (by PIDM) should have an Attribute in LDAP.
Attributes Currently Synchronized (PROD)
- Housing - This Attribute in LDAP is used to identify that someone lives in (or works-for) University Housing. This is currently used to grant access to Xfinity On-Campus television services. (This is actually a combination of the Banner query (who LIVES in Housing) and the Xoc_Xfinity LDAP Group (who works for Housing).)
- ouAdviser - This Attribute in LDAP is used to identity Advisors on-campus. Currently, it grants access to the Advising tab on MySAIL.
Overall Process (Application Flow)
When run, the command line runner BannerAttributeSync syncs attributes as specified in the properties file from Banner to LDAP using the following process. First the application calls the sync() method in the syncService which first requests lists of users with the specified attribute from BannerApi and LdapApi using the BannerAttributeService and LdapAttributeService respectively. These lists are then compared within the syncService to determine which attributes should be added or removed in LDAP.
Once the add and remove list has been built the application uses the LdapAttributeService to call the LdapApi update endpoint to add or remove the attribute for the specified user. After the changes are applied the application uses the PostgresAttributeService to call the PostgresApi endpoint to cache the full list of netIds of users that had an attribute changed.
Additional Support
- OU Technology Center
- 44 Oakland Center
- Rochester, MI 48309-4479
- (248) 370-4357
- Office Hours: M-F 8:00am - 5:00pm