Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0
Warning
titleContent Moved

OSSIDM materials are now maintained at the Jasig FIFER Community of Practice

Wiki space for work on 2010 Advance CAMP Action Item:

Determine Next Steps for Promotion of Open Source IdM Products

 

 

Overview

Deliverables/Goals

Identify and begin executing a strategy for the promotion of OSS IDM products, ie the OSS IDM suite especially for (but not exclusively for) Higher Ed

  • ACAMP Call 2 (Mid Sept): Strategy outline, defined objectives, initial deliverables TBD
  • Jasig Unconference: F2F Meeting
  • I2MM: F2F Meeting
  • ACAMP Call 3 (Mid Nov): Plan for outreach, resourcing, sustained action, second step deliverables TBD

Mailing List

Mailing List: <ossidm@internet2.edu>
To subscribe, send mail to <pubsympa@internet2.edu> with the SUBJECT:

No Format
sub ossidm FirstName LastName

Group Members

Note: Community members who initially signed up were: Jens Hausser (UBC),Todd Piket (MNSCU), Eric Pierce (U South Florida), Randy Miotke (Colorado State U), Dedra Chamberlin (Berkeley); New members: Keith Hazelton (U of Wisconsin-Madison)

Status

  • Spinning up a Jasig Community of Practice
  • Landscape and gap analysis under way
  • Reference architecture underway
  • Marketing collateral inventory under way
  • Establishing a community effort to define service contracts for group interfaces and possibly provisioning interfaces
  • Establishing a clearinghouse for projects such as OpenRegistry and a new provisioning initiative

Working Area

  • Components
    • What's in the box and what's next to the box
    • Architecture diagram
    • Interfaces/Open Standards
      • eg SPML but also EduPerson
    • Existing vs Developing vs Nothing
      • I2 Middleware
      • Jasig
      • Kuali
      • OpenLDAP, 389, Apache DS
      • MIT Kerberos
      • OpenIAM
      • Mural
      • Forgerock
    • IDMaaS?
    • Reference Architecture
    • OSS Stack as a specific "supported" version of each component
  • Marketing
    • Get initial message out to community ASAP
    • Packaging
    • HE focus
    • Favorable licensing of OSS
    • Schwartz: Sun is world's largest open source company
    • TCO
    • Mapping to commercial product functionality
    • CIO outreach
    • Leverage existing name recognition (eg: Kuali)
    • Single label/brand/endorsement?
  • Usability
    • Product standards for documentation
    • Support partners/channels
  • Resources
    • Where will FTE and $$$ come from?
    • Priorities
    • Collaborations

Documents

References