|OIDC-OAuth Deployment WG|
- Solicited community for effective learning materials (sites, books, diagrams, videos, etc.)
- Drafted use case template
- Curate and publish learning materials; identify gaps
- Refine use case template
- Publish initial set of use cases
- Decide our approach to standards profiling
- Identify goals/proposals for TechEx18
- Limited resources and expertise
Streamlining SP Onboarding WG
- Collecting Feedback from Working Group Mailing List
- Shared Working Group material/documents with working group mailing list and collected feedback
- Incorporated this feedback into the Working Group Criteria and Question outline documents
- Criteria Document
- Made clarifications/changes around the recommendations for User Identifiers, Authorization, and Metadata validation/signing.
- Questionnaire (Service Provider Self-Assessment)
- Collected feedback around “helper text” (text that is before and leads up to the question being asked in the self-assessment), to help the onboarding Service Provider understand concepts that included Metadata, Authorization, Attribute Release.
- Two new working group members joined the call
- Continue to supplement (and hopefully finish) the helper text around the self-assessment questions; making it clear to Service Providers what we are asking them.
Attributes for Collaboration and Federation WG
Completed online survey of current InCommon members regarding current and planned R&S Category participation, 132 respondents.
Completed in-depth interviews with a representative sample of InCommon members who do not currently participate in the R&S Category, 7 responding organizations.
Began drafting recommendations.
Deployment Profile WG
- Finishing major revisions to the SAML2int profile
- Preparing a communication and a formal document review of these revisions by the InCommon community
- OASIS will formally vote to approve an OASIS profile that revamps and greatly simplifies federated identifiers
- We’ll be producing a list of items that we didn’t include in SAML2int that fit in a R&E specific deployment profile. We’ll be taking this to TAC to ask if they want us to continue our work or if they want to take advantage of this logical breakpoint to recharter the group. Items we’ve put in SAML2int that get rejected will probably be added to this list.
- We’ve also identified a hand full of federation operator best practices that we’ll be handing to InCommon operations for recommendations.
- None. We’re making good progress and nearing the end of a very intense 18-month journey.