160 likes | 279 Views
UWA Directory Services. David Glance Strategic Projects. Agenda. Requirements Architecture Client Requirements Timeline. Requirements. System provides user information for: Authorisation/Authentication Users Students Staff Groups UnitOfferings CourseOfferings Roles BusinessUnits
E N D
UWA Directory Services David Glance Strategic Projects
Agenda • Requirements • Architecture • Client Requirements • Timeline
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
Requirements (cont…) • User accounts created • Password management controlled centrally through Account Management System (AMS) • Initial password generated
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
Architecture (data import) Active Directory Contacts Exported ldif SRS SRSDownload Imported ldif UserManager HR HRDownload Visitors VisitorDownload MSMQ Campus Card CCDownload
Architecture (data export) Active Directory Client Active Directory UserManager Exported ldif Imported ldif AMS LDAP Directory LDAP Client FNAS Q LDAP Directory MSMQ SOAP Server CSSE Q SOAP Client NIS+ Q Processor ARTS Q File Client Scripts/Programs Synch Manager SOAP Client
Architecture (schema) AD.UWA.EDU.AU BusinessUnits group uwaOrganisationalUnit Roles group uwaRole Users Students inetOrgPerson uwaPerson Staff inetOrgPerson uwaPerson inetOrgPerson uwaPerson InactiveStudents InactiveStaff inetOrgPerson uwaPerson Teaching UnitOfferings group uwaUnitOffering CourseOfferings group uwaCourseOffering
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
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
Architecture (AMS) • Helpdesk • Search for users • Reset password • User provides answer to challenge • Disable/Lock account
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
Client Systems • Critical Clients • SIMS • Validating using LDAP authentication • UCS • Obtaining user names and password information.
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
Timeframe • Equipment purchase and provisioning Mon 11/10/04 • Test system for clients Mon 25/10/04 • Production systems Mon 25/10/04 • Help desk operational Mon 17/01/05 • UCS operational Wed 1/12/04 • Callista operational Wed 8/12/04* • Callista/SRS changeover Fri 8/4/05 • First Round Student Offers Wed 19/01/05 • Documentation for Client Systems Mon 7/02/05
Information • uwads@maillists.uwa.edu.au directory services mailing list • http://www.uwa.edu.au/it/itpo/it_projects/directory_services public project page • David.Glance@uwa.edu.au