The Identity Management Collaborative: A SIMI Pilot Project

1
The Identity Management Collaborative A SIMI
Pilot Project

• Cal Poly San Luis Obispo
• California State University Stanislaus
• The Office of the Chancellor

2
Agenda

• Project Goals and Objectives
• SIMI Status Report
• The Identity Management Collaborative
• Other Items?
• Wrap-up and Next Steps

3
Project Goals

• Provide robust Identity Management services by
  leveraging talent and other resources at one
  campus to serve the needs of a second campus
• Strengthen the operations at the provider campus
• Improve services at the client campus
• Provide test-bed to address issues related to the
  system-wide SIMI Project

4
Objectives

• Create an inter-campus service/support model
• Develop needs assessment tools to determine
  programmatic needs and resources required to meet
  them
• Develop service proposal templates
• Develop performance metrics
• Conduct performance assessments
• Document and disseminate lessons learned within
  the CSU and out to the greater education community

5
Stanislaus

• Project Participants
• Maithreyi Manoharan, Associate Vice President of
  Information Technology
• Russell Inman, Systems Administrator
• Chris Wincentsen, Systems Administrator
• Roland Johnson, Manager Academic and
  Instructional Technology Services
• Becky Atkins, Administrative Analyst/Specialist
• Craig Boucher, Analyst/Programmer
• Robert Fisher, Analyst Programmer
• Corey Cardoza, Analyst Programmer

6
Stanislaus

• Drivers for Participation in SIMI Pilot
• Need for an Enterprise Directory and
  Authentication Services
• Integration of Single sign on for
• Oracle Portal (for email and Banner)
• Blackboard
• PeopleSoft HR 8.0
• Lack of Campus Resources Due to Budget Cuts

7
Stanislaus

• Goals and Objectives
• Authenticating all applications using the
  Enterprise Directory
• Applications considered are Help Desk, Imaging,
  One-Card, Active Directory in labs, Library
• Formalize procedures for adding applications
• Create a knowledge base for both the campus
  community and vendors re authentication
  procedures
• Local hosting of the Directory in a couple of
  years
• Feasibility study to identify resources needed
• Identify migration strategies

8
Stanislaus

• Project Structure
• Identify processes and requirements for a
  successful middleware infrastructure
• Campus buy-in for a remote LDAP directory
• Identify pilot group for training
• Communicate the advantages of a secure identity
  management system on Campus
• Documentation
• Policy statements and agreements
• Creation of knowledge base of Frequently Asked
  Questions

9
Stanislaus

• Benefits
• Collaboration Process
• Learning Process for our staff
• Sharing of best Practices
• Working Directory and Authentication Services
  with minimal effort
• Working knowledge of implementing an Enterprise
  Directory

10
Stanislaus

• Challenges
• Campus and Staff buy-in
• Concept of remote directory services
• Security and reliable access
• Staff resources

11
San Luis Obispo

• Project Participants
• Dan Malone, Middleware Architect
• Ryan Matteson, Enterprise Architect/OCIO Security
  Assurance
• Jason Stratton, Analyst/Programmer
• Theresa May, Coordinator, Information Management
• David Ross, Director, Application and Information
  Management
• Jerry Hanley, Chief Information Officer/Vice
  Provost

12
San Luis Obispo

• Drivers for Participation in SIMI Pilot
• Value of collaboration
• Enables an outside perspective
• Enables knowledge transfer between teams
• Enables feedback regarding processes
• Enables feedback regarding software and tools
  used
• Enables cross-campus collaboration not related to
  middleware (both campuses are implementing Oracle
  Collaboration Suite)
• Service Improvement
• Provides opportunity to enhance infrastructure
• Provides opportunity to improve processes
• Provides opportunity to increase services
• Provides opportunity to improve support
• Provides opportunity to achieve greater economies
  of scale

13
San Luis Obispo

• Goals and Objectives
• Enhance Identity Management Infrastructure
• Upgrade software to newer versions
• Oracle Internet Directory 10g and CAS 2.012
• Implement LDAP replication
• Implement EduPerson/CalStateEduPerson directory
  schema
• Enhance documentation
• technical and procedural
• Enhance cross-campus collaboration
• Facilitate sharing between campuses

14
San Luis Obispo

• Project Structure
• Service Provider
• Providing directory services
• Enterprise LDAP compliant directory
• Providing authentication services
• LDAP authentication
• Web authentication service

15
San Luis Obispo

• Key Deliverables
• Provide a service proposal
• Define security and reliability measures
• Transmission of directory information
• Storage of directory information
• Build and populate an enterprise LDAP-compliant
  directory
• Enable authentication services
• Provide remote support for enterprise directory
  and authentication services

16
San Luis Obispo

• Benefits we hope to gain
• Improved campus buy-in regarding middleware
• CSU sanctioned initiative
• Other CSUs moving forward
• Supports future interaction within CSU system
• Input from other middleware teams regarding Cal
  Polys implementation
• What would another team have done differently?
• Collaboration process
• What can we share? How can we share?
• What did we do right? What needs improvement?
• What did we miss?

17
San Luis Obispo

• Challenges to date
• Resources for the project
• Conflicts with local projects

18
Lessons Learned So Far

• Synchronizing activities at two campuses is not
  trivial
• External forces are also at play
• Receiving help from a provider campus does not
  negate the need to do significant preparation at
  client campus
• Others?

19
If we could have help, wed want

• A web site for campuses to view information
  regarding identity management infrastructures
  within the CSU
• What enterprise LDAP directories are deployed at
  the campuses?
• What is the campus UserID?
• What authentication services are being used?
  What applications have been integrated?
• Etc.

20
Contact Information

• Stanislaus
• Roland Johnson, Manager AITS
• rjohnson_at_csustan.edu
• Maithreyi Manoharan, Assoc.VP for IT
• mmanoharan_at_csustan.edu
• San Luis Obispo
• Dan Malone, Middleware Architect
• dmalone_at_calpoly.edu
• Theresa May, Information Management Coordinator
• tmay_at_calpoly.edu
• Office of the Chancellor
• Mark Crase, Sr. Dir., Tech Infrastructure Srvcs
• mcrase_at_calstate.edu

21

• Questions?

22
(No Transcript)