Identify Gaps in Identity Management

DATE and TIME: May 26, 2011

CONVENER:

SCRIBE: Billy Cook

# of ATTENDEES: 27

MAIN ISSUES DISCUSSED

Topics:
-FIFER - provisioning APIs

-Getting off of Sun IDM

-Identifying gaps in IDM
-A number of groups have been gathering requirements and will work to make them available

-Look at Jasig OpenRegistry project and submit needs

-In industry see virtual directories and master data management products that filter to a directory

-Duke migrating to Oracle but writing their own system that can run almost independently

- ~5 schools interested in Duke’s project
-i2-pr-collab mailing list

-Brown is starting a new system.  Coming up with requirements.

-Need to identify standards we need products to support.

-What is the driver to move to a new system?
- several people say their existing system sucks
          - all rules hardwired in the code
          - scary to make changes (Steve from Brown - brain surgery on an earthworm)

-Big gap in end user self service hub.  How to make easy to use.  Is this an Identity Management or business system problem?

-How are institutions supporting IDM?  IDM team or spread out in the university.  Several schools have an IDM group.  

ACTIVITIES GOING FORWARD / NEXT STEPS

  • Secure environment to have discussions about vendors products
  • Berkeley and FIFER work together to put some documentation out.  
  • Identify people who can answer questions about different IDM systems
  • Use cases, user stories more useful than features in a grid.
     
  • No labels