1 / 28

The IAA Project Status and Next Steps

The IAA Project Status and Next Steps. David Alarie Derrian Jones Tom Jordan Mairéad Martin. Presentation Topics. Background (Mairéad Martin, DoIT) Infrastructure (Derrian Jones, DoIT) Authentication (Tom Jordan, DoIT) Next steps (David Alarie, UWSA). IAA enables.

dane
Download Presentation

The IAA Project Status and Next Steps

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The IAA ProjectStatus and Next Steps David Alarie Derrian Jones Tom Jordan Mairéad Martin

  2. Presentation Topics • Background (Mairéad Martin, DoIT) • Infrastructure (Derrian Jones, DoIT) • Authentication (Tom Jordan, DoIT) • Next steps (David Alarie, UWSA)

  3. IAA enables • System-wide identity management • Efficient implementation of Common System applications • System-wide sharing of expertise

  4. IAA Pilot • March 2001 - July 2003 • Who participated in the pilot? • UW Processing Center • UW Colleges • UW Eau Claire • UW Madison • UW Stout

  5. Current Status • Infrastructure went “Live” July 1, 2003 • Who’s in? • Eight UW institutions: • UW Colleges (NRT) • UW Eau Claire (Batch) • UW Madison (3 systems, all NRT) • UW Milwaukee (Batch) • UW Platteville (Batch) • UW River Falls (Batch) • UW Stout (2 systems, both Batch) • UW Superior (Batch) • And UWPC Payroll (Batch)

  6. Current Status • Who’s left? (IAA Phase II) • Six UW institutions • UW Stevens Point • UW Green Bay • UW La Crosse • UW Whitewater • UW Parkside • UW Oshkosh • And UWPC Student Payroll

  7. IAA White Pages • Provides a simple view into the IAA directory • Shows an individual’s relationship to multiple institutions • Shows role and contact data as submitted by each system of record

  8. IAA Infrastructure Relational Registry Database JOIN RULES Registry Transactions White Pages Authentication Requests TBD TBD TBD TBD TBD TBD Primary Sources The Registry The Directory UW Stout SA LDAP Directory UW Colleges SA XML UW Eau Claire SA SQL LDAP UW Madison SA Registry Clients Directory Clients UWPC Payroll

  9. Methodologies and Concepts • Data Transport • “Secure SQLNet” • Secure Copy (SCP) • Data Pre-processing • MD5 check-summing • Source validation • Data Processing (“Staging”) • Registry business rule compliance • Infrastructure • Person instances • Instance linking (cross-system representation) • Data “ownership” • Data “prioritization” • Content extensibility/supplementation

  10. Source Data Management • Near Real Time (NRT) • Batch

  11. IAA Authentication Hub • Background • IAA decision to avoid a system-wide username • Motivation • Provide AuthN path into system-wide apps • Make use of existing campus infrastructure • Greatly reduce credentialing costs for system-wide apps

  12. IAA Authentication Hub • Design Philosophy • Allow campuses to credential users according to local policy & practice • Allow authentication to happen in campus environment • Provide a tool for campuses to use in integrating system applications • Use IAA infrastructure to convert campus-specific credentials to system-wide identifiers (UWPC PersonID, SPVI, etc) • Get the infrastructure in place to take advantage of opportunities as they arise

  13. IAA Authentication Hub • Project Methodology • AuthN out of scope for pilot, but clearly needed • Comparatively small development effort • Project Drivers • Authentication for Kronos • Strategy for general authentication without central user management • Transition to longer-term technologies (Shibboleth)

  14. IAA Authentication Hub Campus Infrastructure IAA Infrastructure System Application Kronos APBS SFS IAA Registry Campus Portal Campus Users IAA AuthN Hub

  15. IAA Authentication Hub

  16. IAA Authentication Hub • Current Status • Test installation exists • Kronos authentication through My-UW Madison successfully demonstrated • Next Steps • Finish move to production • Look at integration options for other applications • Develop facilities to ease application integration

  17. Next Steps • Remaining tasks in Phase II • Obtaining feeds from six institutions • UW Stevens Point • UW Green Bay • UW La Crosse • UW Whitewater • UW Parkside • UW Oshkosh • Finalize feed from UWPC student payroll • Obtain user credentials for authentication

  18. Next Steps • Remaining tasks in Phase II • Error submission website • Documentation

  19. Next Steps • IAA Governance • Acceptable Use Policy for applications, enhancements, etc. • Application integration (APBS, D2L, Kronos, SFS)

  20. Next Steps • Ongoing funding issue: • Recurring operational costs • Future interface or service development • Proposal for FASTAR to support infrastructure • Staffing requirements • Help Desk and support

  21. Common Systems & IAA • APBS/Lawson • Current authoritative UWPC feeds to IAA will originate from Lawson APBS • The APBS project has invited IAA developers to begin discussions with Lawson developers about what an architecture for external authentication to Lawson would look like. There is no schedule for this yet.

  22. Common Systems & IAA • Shared Financial System /PeopleSoft • SFS will upgrade to PeopleSoft 8.4 in Spring 2004 and will will gain the ability for SFS to authenticate against an external LDAP capable directory • Implementation architecture and timeline not yet discussed

  23. Common Systems & IAA • APBS/Kronos • IAA Auth Hub and a Kronos written servlet are working in a development environment • Use of this mechanism for campus rollouts is dependent on supplementary submission of user credentials to the IAA Registry • Aggressive implementation timeline for UW-Madison

  24. Common Systems & IAA • Endeavor/Voyager • Latest Voyager version installed July '03 provides means to authenticate patrons against an external authentication system • IAA system could provide means for shielding Library Patron identity from content providers • Next step would be to design a common IAA authentication architecture for Voyager/WebVoyage. • An Iliad+IAA implementation appears feasible as well

  25. Common Systems & IAA • Desire2Learn (D2L) • Rollout schedule precludes use of central authentication infrastructure • However, the D2L application can easily transition to an external LDAP based authentication model • Begin integration architecture design and implementation plans (well) after January 1, 2004.

  26. Q&A • More information: http://www.doit.wisc.edu/middleware/iaa/

More Related