...
1. UC Davis' implementation of the Sakai UserDirectoryProvider is located in the ProviderServiceImpl UserDirectoryProviderServiceImpl class in the source tree: Provides both the user authentication and user provisioning into Sakai. UC Davis' implementation of Sakai will perform authentication and user provisioning in the following manner:
a. User authentication: Users are authenticated via DistAuth. In combination with the UC Davis Distributed Authentication Filter LOCATE, user's will be authenticated via SecureWeb. In cases where WebDav is accessed (basic auth), the authentication occurs via the KDC.
b. User provisioning: User's are provisioned upon login via SecureWeb. A query of UC Davis' Mothra (by means of views in external database) will provide all the necessary data to Sakai for creation of user accounts.
...
2. UC Davis' implementation of the Sakai GroupProvider is located in the ProviderServiceImpl GroupProviderServiceImpl class in the source tree: Associates Sakai roles to users, based on particular sites they are accessing. The group provider queries necessary UC Davis external views that contain roles (enterprise level roles such as access, maintain, student, etc.) and also Sakai specific authorization roles at the tool level, component level, etc.
...
3. UC Davis' implementation of the Sakai UserDirectoryProviderCourseManagementProvider is also located in the ProviderServiceImpl CourseManagementProviderServiceImpl class in the source tree: Provides all course related data from Banner via materialized views, and other school data sources as necessary.
...