COmanage can be implemented in three related but distinct ways. Developers should remain aware of separate goals for each path.

1. COmanage can be implemented as a framework, enabling applications to externalize critical identity and access management needs to a common platform. Developers can use the COmanage framework to centrally manage identities, groups, access controls, and other variables across a wide spectrum of domesticated applications.

Deliverables related to this path include:

  • Documentation on domestication
  • Documentation on package check in
  • Documentation on Internet2 software agreements
  • Marketing, dissemination and outreach
  • VOMS comparison and integration
  • Provisioning and deprovisioning discussion
  • Starter kit
  • Coordination between appliance/framework/service
  • Coordination among application domesticators
  • Discussion of plumbing COmanage into the attribute ecosystem

2. COmanage can be implemented as a service. As a service, COmanage is provided by a support center such as a central IT unit, an NREN a federation, or a supercomputing center to users. As a service, implementation strategies, large scale support services, and accommodation of many VOs may become important.

Deliverables related to this path include:

  • Focus on scalability
  • Focus on high availability
  • Specialized documentation for managing multiple VOs in this environment

3. COmanage can also be used as a VM appliance. The open-source appliance provides a drop in set of domesticated applications and the COmanage core platform (where the central identity management is implemented). One question that is yet to be clarified is whether there is a common install/configuration mechanism, which would allow this to be for the use of VOs with only graduate sturents, or whether it is more of a kit that requires a sysadmin. The appliance is intended to grow with new applications as domestication spreads.

Deliverables realted to this path include:

  • Installation scripts
  • Integration with provided domesticated apps
  • Documentation for use

Lead for Framework:  Heather Flanagan

Lead for Service:  TBD

Lead for Appliance:  Digant C Kasundra

  • No labels