SSO Proxy Meetings & Status: Week of 2017-01-23
Date
Attendees
Goals
- Weekly scrum meetings = Tues & Fridays 10:00AM
- Status Update on college proxy integrations
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
Weekly Proxy Scrums Tues & Fridays 10AM | Patty & Matt, Franz & Rodney | Proxy Integration team meets twice weekly on Tuesdays & Fridays to drill down on active Proxy integrations primarily, but also to discuss any open issue related to the Proxy or SSO. *Geneva is no longer on the Proxy team (left on January 1) and replaced by Rodney Hing. Scope of Proxy Team Tasks In addition to the Proxy integration process tasks (See "Steps to Integrate with the CCC SSO Proxy" - the proxy team is also responsible for coordinating the Shibboleth Upgrades for CCC colleges - either by passing them over to Dave Lipari, Unicon, to step in and manage the rest of the steps, or direct the a of colleges that are absolutely "ready" to be integrated with the Proxy Over the past several weeks, we've seen more acknowledgment and understanding from the colleges overall, which is making our job easier doing all the tedious implementation follow-ups, testing confirmations, file uploads etc. must more efficient. In addition to the Shibboleth Upgrades, proxy integrations, and working with the colleges on technical checklist items and troubleshooting, we have had to add the APPLY ADMINISTRATOR / REPORT CENTER metadata replacement tasks (for Pilot & Producton). . Notes and action items - as well as attachments like new metadata are attached to the college/districts Main CIP JIRA ticket. See the CCC SSO Proxy Information and Status confluence page for JIRA tickets, links, details, etc. Thes following colleges were discussed this week - notes and action items are in their main CIP JIRA tickets.
We should consider having Monica attend these twicel weeklu | |
Communication Issues with Colleges NEED to establish policies around communication, IT integration, and documentation | Patty & Matt | Need to discuss communication policy for SSO Requirements and Proxy Integrations. There still seems to be confusion by colleges and team as to "why" are we doing this, what's the benefit of the proxy, why are we storing the CCCID, etc. working on a CCC secure web application, should have a project plan with custom timeline / deadlines based on their timing
| |
Documentation Needs & Tasks | Patty & Matt |
| |
 | Project Management & Hand-Offs |  | Need to have an Implementation PM overseeing the SSO and Proxy - to ensure all aspects of SSO, supported solutions, Readiness Manager (for lack of better word) to ensure colleges know the big picture, as well as project implementation, with the Proxy. Prioritization of colleges is the responsibility of each Project Team and should ensure the Proxy team are kept up-to-date and participate in keeping Pilot colleges and priority colleges at the top of the list and moving forward with Shib Upgrades (when needed), Proxy Integration and testing; specific application configurations and integration (Canvas, CE, Assess, MyPath); and each new proxy integration is also |
Required Proxy Product Development - | Franz | Per Franz, the EPI/MyPath project team called a meeting this week to discuss questions & concerns regarding the "Proxy Sign-In Screen for Unauthenticated Users" (see screen shot below). This page was developed outside of Patty's knowledge so she doesn't have requirements. - The workflow is: students are hitting MyPath directly (CCCCO workflow) and when "Signing In" they encounter this screen with drop down menu showing only those colleges that have integrated with the Proxy. This is confusing to the team and ultimately to end users.
| |
Questions from Steve Klein re: the Proxy, SSO, etc. | Steve Klein | Steve sent out an email to Lou, Tim and Patty (dated 1/23/17) with a series of questions about Shibboleth upgrades and proxy integration process. These questions have been asked and answered many times in the past, but Steve is just catching up with the whole process | |
Discussion during PM meeting on Tuesday 1/24 | Parker | Only a few people showed to this week's PM meeting, but Patty put "Issues around CCCID transfer process" on the agenda, as well as general discussion about Support and integration implementation workflow for priority colleges moving forward with the proxy. These issues were posed to Lou, Tim and Patty by Steve Klien | |
SSO Sync Meeting - Friday 1:30PM | Jon Fanucci |
| |
SSO CCCID Discussion Meeting with OEI Team Friday 1/27 3:30PM | Patty & Matt; John Sills, Steve Klein & Monica | Patty, Matt and John Sills chatted earlier this week to discuss the issues the OEI team is encountering for ensuring the colleges store the CCCIDs in theirStudent Information System (SIS).Though colleges have agreed vis MOU to store the CCCID when they implemented Apply, the MOU didn't specify they had to store it in AD or SIS, so many colleges weren't storing it in functional way. was around getting the proxy-created |
Need to discuss communication policy for SSO Requirements and Proxy Integrations
- HIGH PRIORITY NEED: Each college should be given a Project (or PILOT) Implementation Plan & Timeline Agreement which outlines the SSO and proxy integration tasks included in the overall Pilot Project.
- TEMPLATE: This should be a template so that all CCC Projects are using the same language, same requirements, same processes and contact info, etc. Should be short and sweet, concise with links to online documentation.
- DRAFT: Proxy team should do first DRAFT and Colleges/or Park submit to Product Managers for feedback and revisions. (determine timeline on this). Patty & Matt include section for Application or Pilot-specific information and requriiements [can work with Product Managers to develop a standard template shell and each PM can customize it for their projects or pilot needs) - developed by the CCC Project Team - outlining the project implementation requirements (including the technical requirements for SSO and proxy).
- The project plan should include information or links to information relative to the Application or PILOT project and what are System Requirements, deadlines, etc. including high level > details about the CCC SSO initiative, requirements around compliance for IdP solution (SAML) and
- Add this to the 1/31 Product Manager's Meeting agenda -
- These should be Google doc or sheet - stored in Shared Google drive - relative to the college
- There still seems to be confusion by colleges and team as to "why" are we doing this, what's the benefit of the proxy, why are we storing the CCCID, etc. working on a CCC secure web application, should have a project plan with custom timeline / deadlines based on their timing