Page History

1. Define a CO
2. Configure CO Enrollment Flow
3. Enroll person
4. Approve person
5. Search for person in Directory
6. Login to Dokuwiki as person
7. Expire person
8. Search for person in Directory
9. Login to Dokuwiki as person

Background

This script utilizes two roles intended to demonstrate the platform:

1. U1: A new member of the Demo CO
2. P1: The Demo CO Admin

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 Registry demonstration installation available at https://demo.co.internet2.edu/registry.

The "Demo Directory" refers to the COmanage Directory demonstration installation available at https://demo.co.internet2.edu/directory.

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):

1. Each presenter who will perform P1 must have the organizational identity for the P1 login they will use for the demo added to or used to login to the Demo IDMS.
   1. "Organizational Identities" -> "Add a New Organizational Person"
   2. Be sure to add an email address (so the identity can be invited to MyCO).
   3. 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.
2. Each P1 login organizational identity must be invited to Demo.
3. Each P1 login MyCO identity must be added to the group Demo:admin.

Pre-Demo Checklist

1. Remove U1 login from Demo and delete the organizational identity from the Demo IDMS.
2. Remove enrollment flows from previous demos.
3. Delete any previous demo pages from the Demo Wiki.
4. Delete any previous Extended Attributes

Introduction (5 min)

1. roll call
2. validation of sound quality
3. review of purpose of the demo
4. pause for questions at end of every section

Domain and Language (10 min)

1. Show Enrollment flow diagrams
   1. "These are the most common paths for getting individuals in to a VO, based on our discussions to date"
   2. "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."
2. Note that ideally, all this presupposes participating institutions are part of a federation

COmanage Technical demo (25 min)

1. P1 logs into Registry
2. P1 creates a new Enrollment Flow
   1. Enable CO or COU Admin Enrollment
   2. Require Approval
   3. Define attributes
      1. COU, CO Person
      2. Name, Official, Org Identity
      3. Email, Office, Org Identity
      4. Identifier, ePPN, Org Identity, Login
      5. Organization, Org Identity
      6. Affiliation, Org Identity
      7. Name, Preferred, CO Person
      8. Title, CO Person Role
      9. Email, Office, CO Person
      10. Address, Office, CO Person Role
      11. Telephone Number, Office, CO Person Role
      12. Affiliation, CO Person Role
      13. Valid From, CO Person Role
      14. Valid Through, CO Person Role
3. P1 defines a new Extended Attribute
4. P1 adds the Extended Attribute to the Enrollment Flow
5. P1 adds an Extended Type (show off in Enrollment Flow?)
6. P1 defines a new Identifier Assignment
   1. This identifier will auto-populate an email address upon approval
7. P1 execute new Enrollment Flow ("My Population" > "Enroll")
   1. Explicitly create an email address OR tell the new Identifier to create an email address
   2. Demonstrate real-time matching on preferred name attribute (first 'joh', pause 'n', last: 'a' should work in co name)
   3. P1 adds new Person with Organizational Identifier as asserted by U1's IdP
   4. Add a Telephone Number and Address to show in Directory
8. P1 approves the petition
   1. Show off email address auto-populated by identifier assignment execution via enrollment flow
9. P1 searches for U1 in Directory
10. P1 also demonstrates type ahead
11. P1 adds U1 to Dokuwiki group
12. U1 login to the wiki
13. U1 logs out of wiki
14. P1 returns to Registry
15. P1 sets expiration date to be in the past
16. P1 searches for U1 in Directory
17. U1 attempts to login to the wiki again

Other

Optional items if applicable to audience

1. REST API
2. Discuss what kind of attributes an institution might need to release to make this useful

Closing (10 min)

1. final questions
2. review utility of the demo - was this useful?
3. set up another call in 1-2 weeks to answer any questions that might have come up

Post-Demo Checklist

1. 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.
2. Perform the cleanups described in the Pre-Demo Checklist so they don't have to be done next time