Are there any strategies that should be added (or dropped)?
We'd like to complete this phase of the work by our 9/17 call. If you are a fact finder, please spend some time on your strategy before this 9/3 call so that we can discuss any questions you may have.
Implementation vs. Deployment
Do we want to restructure into two tables? If so, what new structure do we want?
Call Notes
Attendees
Shaun Abshere, WiscNet
David Alexander, IdM Integration
Mark Beadles, OARnet
Steve Carmody, Brown University
Dedra Chamberlin, Cirrus Identity
Emmett Culley, California Community Colleges
Scott Koranda, Spherical Cow Group
Ben Poliakoff, Reed College
Tom Scavo, Internet2
Mark Scheible, MCNC
Progress of initial strategy assessments
The column about support for authentication contexts, multifactor, and assurance is about Multi-Context Broker-like functionality, where the IdP can respond properly to requests from different authentication contexts from SPs.
David will announce a process for fact finders for submitting their strategy assessments.
Please complete your assessments by our next call (9/17/2014).
We agreed to add Pros and Cons columns to the assessment table.
Implementation vs. Deployment
"Implementation" refers to capabilities of the software used to implement the IdP, how it's configured, etc.
"Deployment" refers more to the higher-level deployment strategy (e.g., run locally, outsource as a cloud service).
We will readdress this issue after we've done our fact finding. The table has been useful in helping us understand what to collect, but that may not be the best way to present our findings.
Action Items
David will announce a process for fact finders for submitting their strategy assessments. (done)
David will add Pros / Benefits and Cons / Risks to the table and the template. (done)
Please complete your assessments by our next call (9/17/2014).