COmanage Developers List

[Benn Oshrin <>]

-------- Forwarded Message --------
Subject:        [tier-architecture] TechEx Invitation: TIER Adoption Cohort,
Dev & WG F2F Meeting
Date:   Tue, 1 Aug 2017 22:06:24 +0000
From:   Steven Zoppi 
<>
Reply-To:       

To:     

<>,

 
<>,

 
<>,

 
<>




_Invitation to all Trust and Identity Technologists_


The Working Group, Development and TIER Campus Success Cohort
Face-to-Face Meeting is a unique opportunity, TWICE a year (Global
Summit and Technology Exchange) to interact with each other, talk
directly to the */community's technology leadership/*, and provide
feedback in a way that is impossible to achieve in any other venue.


*This meeting (3 1/2 hours) will focus on:*


*Preview of Year-End 2017 -> Full-Year 2018 Completion of
Program-related Technology Goals*

* *

*/NOTE: /**/Participants will be asked to prepare prior to the meeting
by reading materials that will be supplied prior to the session since
our focus will be on interactive discussion./*


*Our meeting will be held at the 2017 Technology Exchange in San
Francisco on:*


*Thurs**day,** Oct**.** **19**, **2017, from **12:30** **pm to
4**:00 **pm** (following the close of Advanced CAMP)*

*Seating will be limited to 45 Participants*


  * *_Register Here

<https://docs.google.com/spreadsheets/d/1aNviIwPauAuWZGqjxbhQnB5VfTRx_1Iiey9hWdFez98/edit?usp=sharing>_*

  * Lunch will be provided at noon, following the close of Advanced CAMP.

  * The TIER Program is picking up the cost for this session, so it’s
    *free to attendees*(as it has always been)

  * Please start sharing this information to those in your teams who are
    interested in participating in the discussions.


*Meeting Goals*

Based on participant feedback, the meeting goals are:


·         Facilitate interaction of attending Working
Group contributors directly ... ACROSS all the TIER Program working and
Campus Success Cohort groups.

·         Ensure consistency regarding the understanding of key
issues/challenges/accomplishments being addressed by the working groups.

·         Survey and AFFIRM or COURSE-CORRECT the working group
direction from a community perspective.

o    Review Work Completed

o    Ratify the direction for the next phase(s)
o    Feedback Solicitation and Preview of Year-End 2017 and Full-Year
2018 Completion Goals


We will**continue to refine the purpose and goals of this meeting based
on participant feedback to ensure that we make the best possible use of
everyone's time.

*Agenda*

* *

  * Welcome and Participant Introductions (15 Minutes)
  * Overview of the Working Groups’ Labor Planning Results (10 Minutes)
  * Progress on notable items from the /Break and Breakout Session /of
    Global Summit (10 Minutes)
  * Introduction / Feedback on /Instrumentation Proposal/ (10 Minutes)


Working and Development Group "*Interactive Lightening Rounds*"


  * *CACTI (Community Architecture Committee for Trust and Identity)
    *Inaugural Introduction and Initial Objectives (15 Minutes)


  * *Review / Ratify / Feedback* Solicitation for Working Groups (45
    Minutes/10 Minutes + 5 Minutes Each for Q/A/Feedback)


§  Packaging

§  API and Data Structures

§  Entity Registry


  * *BREAK (15 Minutes) & FEEDBACK BREAKOUT (30 Minutes)*


§  This section enables the participants to summarize, through swift
breakout sessions, the top 3 or 4 insights regarding how well Working
and Development Groups are progressing in meeting adoption
needs. *(Global Summit Face to Face Meeting Results are shown below)*

·         Architecture / Infrastructure

o     "What's Working Well" versus "What Needs More Attention"
·         The attendees will be divided into 2 groups to candidly assess
how well (or not) our direction is meeting the needs.


  * *Review / Ratify / Feedback* for Components  (50 Minutes/10 Minutes
    Each)


§  Shibboleth

§  Grouper

§  COmanage

§  Federation Operations

§  Consent


  * *Wrap-up (5 minutes)*




Global Summit TIER Technology Community Face to Face / Break and
Breakout Session Summary:

*/Top Issues/*

        

*Architecture *

        

*Ops/Infrastructure *

        

*Notes and Comments*

*/Working Well/*

        

·         There is a defined vision for what the person registry should be
·         Provisioning has separated from authorization and establishing
a TIER pattern for groups
·         Architecture and packaging WGs have come together so that we
can prototype concepts and create working examples
        

·         Actually doing it
·         Grouper Deployment Guide
·         Tooling pipeline
·         Small greenfield deployment is actually easier
        

*/Needs Attention/*

        

·         Documentation on practices so institutions can determine how
TIER will work on their campuses
·         Documentation around the intended components and canonical
interactions so they can be broken down and analyzed to address security
·         Focus on small schools and adoption and engagement with
vendors such as Aegis and Fischer who are interested in using the TIER APIs
        

·         Lessons learned/post-mortem of issues
·         Need for documentation
·         Need security (vulnerability) testing and functional testing
·         Operational bandwidth/resistance to change. Show the value-add
that inverts this problem so they see the motivator
·         Some use cases are hard right now (O365)
        

·         we haven't taken the time to do this and that would be valuable
·         from ground up
·         Need automated smoke testing at a minimum
·         Maybe should list and prioritize these types of use cases with
wider community






*:: *Steven Zoppi**

*:: */AVP, Services Integration and Architecture/**

*:: 
*//

* *

*:: **Internet**/2/**/®/***

*:: *6001 Shellmound St Suite 850

*:: *Emeryville, Ca  94608

*:: *p: 510 858 0884 ▪ m: 415 279 1650 ▪ f(office): 510 858 0894 ▪
f(digital): 877 313 2002 x708
*:: *SJZoppi @ [ Skype :: MSN :: AIM :: Y! :: GTalk ]