1. UWA Directory Services David Glance Strategic Projects

2. Agenda Requirements Architecture Client Requirements Timeline

3. Requirements System provides user information for: Authorisation/Authentication Users Students Staff Groups UnitOfferings CourseOfferings Roles BusinessUnits Data comes from defined sources SRS/Callista HR Visitor Information (Library) UCS

4. Requirements (cont…) User accounts created Password management controlled centrally through Account Management System (AMS) Initial password generated

5. Requirements (cont…) Data passed to designated client systems SSL and/or IPSec Client needs to be authorised to receive data Permission to access data from data custodians: Student Services Library Campus Card UCS

6. Architecture (data import) SRS HR SRSDownload HRDownload Active Directory UserManager Contacts Visitors Campus Card VisitorDownload CCDownload Exported ldif Imported ldif MSM Q

7. Architecture (data export) Active Directory UserManager Exported ldif Imported ldif MSM Q Q Processor FNAS Q CSSE Q ARTS Q LDAP Client SOAP Client File Client Client Active Directory Synch Manager AMSLDAP Directory SOAP Server LDAP Directory NIS+ Scripts/Programs SOAP Client

8. Architecture (schema) AD.UWA.EDU.AU BusinessUnitsgroup uwaOrganisationalUnit Users Students Staff InactiveStudents InactiveStaff Teaching UnitOfferings CourseOfferingsgroup uwaCourseOffering group uwaUnitOffering inetOrgPerson uwaPerson Rolesgroup uwaRole

9. Architecture (AMS) Account Management System Prime requirement for web based interaction No PIN? May allow PIN as initial password Use student number or username as account name. User component Initial password, change password, Help desk Reset password, disable, lock account

10. Architecture (AMS) User Create initial password Provide details (Birth date, Student/Staff Number) Provide challenge question and answer Change password Supply the challenge/response Change details

11. Architecture (AMS) Helpdesk Search for users Reset password User provides answer to challenge Disable/Lock account

12. Client Systems Can choose: Ignore system altogether Just get files (ldif changes or unprocessed atrribute/value files) Elect to get static data but ignore password changes Use SOAP server (C# or Python) Use file changes LDAP update Setup Active Directory to synchronize off of central AD

13. Client Systems Critical Clients SIMS Validating using LDAP authentication UCS Obtaining user names and password information.

14. Client Systems Requirements Choose method of access Get permission for data being used Allocate a server for communication Use SSL or IPSec All local mechanisms for password changing needs to be disabled Update all user documentation, web pages, etc. for the new system

15. Timeframe Equipment purchase and provisioningMon 11/10/04 Test system for clientsMon 25/10/04 Production systemsMon 25/10/04 Help desk operationalMon 17/01/05 UCS operationalWed 1/12/04 Callista operationalWed 8/12/04* Callista/SRS changeoverFri 8/4/05 First Round Student OffersWed 19/01/05 Documentation for Client SystemsMon 7/02/05

16. Information uwads@maillists.uwa.edu.au directory services mailing list uwads@maillists.uwa.edu.au http://www.uwa.edu.au/it/itpo/it_projects/ directory_services public project page http://www.uwa.edu.au/it/itpo/it_projects/ directory_services David.Glance@uwa.edu.au