IAMUCLA
Child pages
  • IAMUCLARoadmap

Versions Compared

Old Version 68

changes.mady.by.user Wu, Albert

Saved on

compared with

New Version 69

changes.mady.by.user Wu, Albert

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

iamucla
Project Roadmap

iamucla
iamucla is a set of services aimed to help campus applications manage the process of establishing who you are and what access you have in a way that is simplified, structured, and streamlined. The project began in 2004 as the EDIMI project. It was renamed
iamucla
when the project was funded to develop its access management phase in 2007. The following is the project roadmap:

Deliverables within the "EDIMI" Project Scope

Planning Phase

Duration

First half of 2004.

Activities

  • Gather Functional Requirement
  • Define UCLA Enterprise identity management architecture
  • Prepare Project Control Document

Milestones

  • PCD endored by CITI. Project funded under UTIPP - Q3, 2004

Phase I - Basic Infrastructure

Duration

Q3 2004 to Q4 2005

Activities

  • Re-architect BOL to split out the login ID space from other BOL services.
  • Update ISIS to interoperate with Shibboleth
  • Install and pilot Shibboleth
  • Develop Enterprise Directory schema and configuration
  • Deploy Enterprise Directory into limited production

Milestones

  • UCLA Logon relaunched as a separate service from BOL - Q4, 2005
  • Enterprise Directory enters limited production - Q4, 2005

Phase II - Stabilizing EDIMI Services

Duration

Q1 2006 through Q1 2007

Activities

  • Launch ISIS 5
  • Integrate URSA with UCLA Logon account provisioning
  • Launch Shibboleth into production
  • Revise Enterprise Directory as needed

Milestones

  • ISIS 5 Launch - Q3, 2006
  • Shibboleth enters production - Q3, 2006
  • Enterprise Directory enters full production - Q3, 2006
  • URSA launches with UCLA Logon provisioning and ISIS integration - Q4, 2006

Phase III - Deploying EDIMI Services; Next Step Planning

Duration

Q1 2007 through Q4 2009

Activities

  • Migrate campus ISIS applications to Shibboleth
  • Update email collection workflow
  • Develop plan for access management services

Milestones

  • Pilot Adoption of Shibboleth - 2007
    • CCLE adopts Shibboleth
    • myevents.ucla.edu adopts Shibboleth
    • UC At-Your-Service joins UCTrust and adopts Shibboleth for federated single sign-on
    • UC Learning Management System joins UCTrust and adopts Shibboleth for federated single sign-on
  • Launch official campus ISIS to Shibboleth Migration Program - March, 2008

Moving Forward with
iamucla

Access Management - Planning

Duration

2007 - Q2 2008

Activities

  • Gather Functional Requirement
  • Define UCLA Access Management architecture
  • Prepare Project Control Document
  • Submit project proposal for funding approval

Milestones

  • Project endored by CITI. Project funded under UTIPP2 - Q4, 2007
  • Official temporary funding released - Q1, 2008

Access Management - Developing the Prototype

Duration

Q2 2008 through Q2 2009

Activities

  • Install, configure, and test Grouper;
  • Update Enterprise Directory to accommodate group data;
  • Conduct Grouper pilot;
  • Form policy and practices workgroups to determine best practices and procedures;
  • Install, configure, and test Signet;
  • Conduct pilot with target to be named Design DACSS-to-Signet replacement process;

Access Management - Scaling for the full campus

Duration

Q2 2009 through Q4 2009

Activities

  • Design and deploy help desk support procedures;
  • Identify a list of integration targets for future integration
  • Enter DACSS2 (Signet) pilot

Full Deployment and Stabilization

Duration

Q1 2010 and beyond

Activities

  • Rollout DACSS2 (Signet)
  • Continue to integrate additional systems with
    iamucla
    services;
  • Identify future
    iamucla
    related activities