Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

    • SteveZ noted that the Internet2 Trust and Identity software  projects are independent.  There will be an effort in 2021 to come up with high level overview of goals/activities
      • Keith Hazelton leads a software integration working group (meets twice per week) talking about interoperability of the TAP components. Dealing with much complexity from the four components. BillT sometimes attends that group. 
      • IAM is an integration exercise and there is a palette of tools
      • The search for an “easy button” may be a search in vain
        • Participants need to understand how things work, well enough to be accountable when running them.
        • "I can explain it to you, but I can't understand it for you."
      • Internet2 Trust and Identity can invest in technology or in training/education, but with limited resources cannot invest fully in both at the same time
      • TIER started with prioritization of technology
      • Later a shift was made to invest in training, thus the Collaboration Success Program
      • There can be some conflict of opinion on how to package components
        •  Creation of containers with many choices
          • or
        • decorate containers with many knobs
          • or
        • deploy and maintain some number (like 3) patterns
      • There are tradeoffs  
      • Component Architects prefer to maintain patterns that describe about 80% of cases, 
      • Supplement with proper training
      •  Grouper Deployment Guide provides patterns
      • It may be helpful to have a smaller number of architectural patterns with better connectivity between practitioners
    • Question whether the community has difficulty deploying the individual components
      • Or overall architecture problem of “how do I implement IAM with the ITAP tools?"
    • Commercial Service providers complexity causes challenge
    •  Asking major commercial service providers to change their patterns for identity control is generally an uphill battle
    • Tom: Suggestion for CACTI  CACTI in 2021 : exercise leadership across the working groups on this issue of reference implementations
    • SteveZ: CACTI members are welcome to join the working group calls where implementation patterns are discussed
    • SteveZ: Sandbench concept is being developed.
      • AI: Solicit topics from new members. Tee up on Dec. 22, 2020 CACTI call, continue into first meetings of 2021.


Parking Lot

  1. (From June 9, 2020 call) TomJ  - Add as an agenda item for a future CACTI call: Operationalizing containers
  2. Representation/shared leadership across TAP groups such as component architects and software integration. (from Dec. 8 call)

...