BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

12
BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

description

BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World. UW-Madison. History/Current IdM Infrastructure. Next up: Populations, Affiliations and Service Entitlements (PASE). Business Drivers. - PowerPoint PPT Presentation

Transcript of BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

Page 1: BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTUREReports from the Real World

Page 2: BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

UW-Madison

Page 3: BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

History/Current IdM Infrastructure

Page 4: BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

Next up: Populations, Affiliations and Service Entitlements (PASE)

Page 5: BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

Business Drivers

• Efficiently manage the identities of persons and their relationship with the university.

• Securely and effectively conduct business with other institutions and government agencies.

• Examples:– Granting a visiting professor access to the network and course

management system.– Giving non-university employees (e.g. UW Hospital) to university

managed resources (e.g. parking).– Providing new hires with an email address to receive employment

communications before they begin work.

Page 6: BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

Requirements

• Rapid response to customer requests– New affiliations (groups)– Access to services by new or existing affiliations

• A stable and reliable authorization infrastructure• Standard provisioning processes• Standard system interfaces for accessing group and entitlement

information• Support for large numbers of affiliations and diverse populations• Better visibility into who has access to service• Improved audit and logging capability • Reduce the need for custom development when addressing customer

requests

Page 7: BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

The Concept

Page 8: BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

Approach/History

• Improved reconciliation process• Developed standard interface to the UDS• 2001 - Started PASE

– Made the decision use internal development• Enabled the registry (UDS) to store affiliation data• A lot of project ups and downs. Changes is staff and management• 2005 - Reinitiated UI requirements gathering

– Looked like it was going to take a long time• Decided to step back, do a survey of the market

– Did a build vs. acquire analysis• Determined that acquiring a solution would be the most time-efficient and

economical path• Acquired a real project manager• Adopted and implemented a rigorous

project management mindset

Page 9: BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

Project Approach

Page 10: BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

Governance/Policy Roadmap

Page 11: BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

Technology Gaps/Roadmap in more detail

Page 12: BUILDING A DISTRIBUTED ACCESS MANAGEMENT INFRASTRUCTURE Reports from the Real World

The PASE Team

• Chris Holsman - Executive Sponsor• Pam Allen - Project Manager• Monica Crawford - Lead Developer• Steve Devoti - Enterprise Architect• Chuck Miller - Business Analyst• Mark Weber - Solution Architect• Keith Hazelton - Enterprise Architect