1. Identity Management Integration CAMP
Forming Your Game Plan and Next Steps
Noreen Hogan
University of Oregon
June 29, 2005

2. Dealing with challenges
Making the IdM project a priority
Competing with other projects for staff time
Prioritizing tasks and moving forward with the IdM project

3. Making the IdM Project a Priority
Communicate to keep project visible to
gain support, trust, and participation
Project web site
Design documents, affiliation definitions, etc.
Mailing lists
Central IT technical group
Policy Committee
Meetings
Central IT staff as needed
Other interested groups on campus
Publications
IT strategic plan, Newsletters

4. Competing With Other Projects
Planning and Timelines
If you don't set a timeline, then other projects
that are more established or that have deadlines
will take priority.
Considerations
When is a good time to introduce a new service or major change in service to campus?
What can you realistically accomplish with existing staff and resources?
Is it possible to increase staffing?
Keeping project visible, documenting progress, and gaining support of key people were big factors in our gaining approval to add a new position.

5. Prioritizing Tasks Within The IdM Project
Biggest problem areas at UO
Timely provisioning of services and removal of service access
Faculty need for access to course management system one term prior to start of contract to set up course site.
Managing identity information for people other than traditional faculty/staff/students
Many tracked manually, minimal identity information
Limited and inadequate centralized authN services
Credential for ERP self-service web application managed separately than credential for other central services.

6. Prioritizing Tasks Within The IdM Project
Phased implementation
1. New credential and service provisioning
system that more tightly integrates with ERP data
and also tracks identity info for entities not in ERP.
Start with re-working Person/Identity Registry
Then Credential/Service Provisioning Registry
2. Central authN, beginning with centrally managed services, then add additional campus services.
3. Central Authorization services
Initially we will store affiliations in the directory for this purpose, but other authZ in future.

7. Moving Forward With The IdM Project
Decision making (policy and technical)
Provide specific options for review and feedback
Suggest direction and move forward if no major objections
Keeping big picture in mind while focusing on smaller tasks
Design for future needs
Dynamic rule sets for affiliations. Easily changed as policy and business practices evolve.
Build in ability to deal with and track exceptions
Modular design/api model to minimize impact of modifications