You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Page is very much a work in progress.

Characteristics found in this use case: A single platform managed by a single, central organization, with multiple, discrete VOs each with their own enrollment processes ; enrollment processes include self-signup, administrative/delegated signup, and conscripted signup; primarily campus IdP with support for federated identities; apps include typical collaboration apps we well as domain specific apps, ssh key management, github access; need to demonstrate audit capabilities for grant reporting

 

Before you login

  1. think about what structure you need for your platform.
    1. If you want members of one CO to see the members of another CO
    2. If you want to delegate as much of the user and enrollment management as possible

 

Need more here re: the definitions, and pros / cons of CO/COU structure

Need a pointer to how to connect apps to the registry

 

 

Steps to set up your first VO

  1. The site administrator will have set up the first CO; this is the one CO that bootstraps all the rest. You will need to be enrolled in that CO and set up as a platform administrator.
    1. "Platform Administrators are configured by adding the appropriate Organizational Identity to the COmanage, and then adding the corresponding person to the admin group within the COmanage CO."
  2. Go to the COmanage Registry URL (address TBD for your site). During the installation process, the site administrator should have set up the discovery service so you can login with your institution's preferred IdP.

 

Delegating Administration

  1. Creating CO administrators
  2. Creating COU administrators

 

Enrollment in a CO

 

Groups and COUs

  • No labels