Background
This script utilizes four roles intended to demonstrate the platform:
- U1: An unprivileged, existing member of MyCO
- U2: An unprivileged new member who will be added to MyCO and made a COU Admin
- P1: The MyCO CO Admin
- P2: The CMP Admin
It is possible to run this demo with one person performing all four roles, or with four people each performing one role, or with two people each performing two roles. Where a person performs more than one role, it may make sense to use protectnetwork identities for the unprivileged roles and organizational identifies for the privileged roles.
An abbreviated demo only uses two roles (P2 and presenter's choice of U1 or U2), and therefore covers slightly less.
The login identity or EPPN (such as foo@idp.protectnetwork.org or bar@internet2.edu) associated with each role will be referred to as a "login" for short, eg: U1 login.
The "Demo IDMS" refers to the COmanage Gears demonstration installation available at https://demo.co.internet2.edu/gears.
The "Demo Wiki" refers to the Dokuwiki demonstration installation available at https://demo.co.internet2.edu/dokuwiki.
Presenter Requirements
The following must be done for each presenter once (not once per presentation):
- Each presenter who will perform U1, P1, or P2 must have the organizational identity for the U1/P1/P2 login they will use for the demo added to the Demo IDMS.
- "Organizational Identities" -> "Add a New Organizational Person"
- Be sure to add an email address (so the identity can be invited to MyCO).
- Be sure to add the EPPN as an identifier and check the "login" box so it can be used to login to the Demo IDMS.
- Each U1 or P1 login organizational identity must be invited to MyCO.
- Each P2 login organizational identity must be invited to COmanage.
- Each U1 login MyCO identity must be added to the group MyCO:dokuwiki.
- Each P1 login MyCO identity must be added to the group MyCO:admin.
- Each P2 login COmanage identity must be added to the group COmanage:admin.
Pre-Demo Checklist
- If P1 login also ordinarily has CMP Admin privileges (ie: is a member of COmanage:admin), remove the COmanage:admin group membership.
- Delete demo group MyCO:North American Researchers if it exists.
- Remove U2 login from MyCO and delete the organizational identity from the Demo IDMS.
- Delete any previous demo pages from the Demo Wiki.
- Remove U2 from the group MyCO:admin:TestCOU2.
Introduction (5 min)
- roll call
- validation of sound quality
- review of purpose of the demo
- pause for questions at end of every section
Domain and Language (10 min)
- show Intake and Enrollment flow diagrams
- "These are the most common paths for getting individuals in to a VO, based on our discussions to date"
- "How this is looks to the users of the CMP may vary. We'll look at what COmanage itself would look like out of the box, then look at how it might be implemented behind the scenes in a more branded, portal environment."
- Note that ideally, all this presupposes participating institutions are part of a federation
COmanage demo site (35 min)
Content |
Standard Demo |
Abbreviated Demo |
---|---|---|
User Perspective |
|
If performing U1:
|
CO Admin Perspective |
|
|
COU Admin Perspective |
|
If performing U2:
|
CO Platform Management |
|
Perform steps 1-5 |
Other
Optional items if applicable to audience
- LDAP query
- REST API
- Discuss what kind of attributes an institution might need to release to make this useful
Closing (10 min)
- final questions
- review utility of the demo - was this useful?
- set up another call in 1-2 weeks to answer any questions that might have come up
Post-Demo Checklist
- If P1 login ordinarily has CMP Admin privileges (ie: is a member of COmanage:admin), but they were removed in the Pre-Demo Checklist, add a COmanage:admin group membership.
- Perform the cleanups described in the Pre-Demo Checklist so they don't have to be done next time