Summary
The CCC Technology Center has received multiple concerns from a handful of colleges that have implemented the SSO proxy -or are in-process of implementing the SSO proxy - as a requirement to their Canvas LMS adoption.
The issues that we are hearing from the colleges are:
- The Proxy is creating confusion amongst students - barrier to a legitimate workflow they are expecting
- College faculty & staff have not been informed on the Proxy
- The Proxy UI is not user-friendly - doesn't provide enough information about what it is and why are they seeing this?
- The Proxy UX is not user-friendly - doesn't provide a streamlined process
Issues & Concerns | Proposed Solutions | |||
---|---|---|---|---|
Canvas Proxy Integration Requirement | ||||
A | Several colleges who have implemented Canvas have raised concerns about the requirement to implement the proxy workflow and haven't chosen not to do so to avoid the challenges and frustration to their students, faculty, staff and IT. | To support the colleges that are not ready for Fall 2018:
Colleges need more information and options from the Tech Center on how to implement the proxy for Canvas.
| ||
B | These colleges have completed the required IT integration, but either didn't fully understand the workflow through the proxy, or didn't prepare operationally for the workflow changes | |||
C | Faculty and staff have complained that they are getting redirected to the proxy as well as students and it's catching them off guard. The college had not informed/trained staff and faculty, or the information wasn't understood by the college during IT integration. | |||
D | Some colleges don't want to implement the proxy workflow this fall until better implementation support and training is provided by the Tech Center. | |||
These are the colleges that we heard from:
| ||||
Proxy Perception Issues | ||||
A | Overall, colleges do not understand the purpose of the SSO proxy: how it works, why it's important, and how it is related to OpenCCC (or CCCApply or the CCCID). Admissions & Records and IT seem to have an understanding of the systemwide CCCID, but in general, college faculty, staff, counselors, and even college/district leadership hasn't been exposed to the significance of the CCCID and how it's used to track student records across the CCC system over the lifetime of the student's educational journey. | The Tech Center needs to develop a clear, consistent message about the significance of OpenCCC, the CCCID for all students, and the SSO Proxy --- providing information on the purpose, the requirements, the long-term goals and objectives of the systemwide ID for all students - AND outline the implementation options and plan for communication to students and staff. | ||
B | Colleges that adopted OpenCCCApply years ago never stored the CCCID in their SIS, thus the processes are not in place to implement the full workflow process | Outline process for communication to students about the OpenCCC Account and CCCID How it's different from their college student ID and used for systemwide single sign-on and tracking across colleges and applications | ||
C | Based on feedback from colleges, students perceive the proxy to be illegitimate ("Is this for real?"). It appears to be a phishing attempt or scam, and doesn't feel congruent to their expectation that they were on their way to Canvas from their college portal.. | Implement short-term improvements to the Proxy Sign-In page with better messaging, college branding, application branding, support for students with a video tutorial and a link to support. | ||
D | Colleges perceive the proxy as a barrier for their students | Provide colleges with information on importance of the CCCID and the SSO proxy; Provide colleges with information and options to prevent the proxy from re-directing students, including ensuring IdP and common directory is passing the information required by the proxy | ||
E | Faculty and staff perceive the proxy as a barrier for them - they are frustrated | Provide the colleges with information on the importance of passing the correct attributes in metadata Whitelist (temporarily) Canvas, Starfish, Other vendor applications, and CAP to prevent faculty, staff from being re-directed to the proxy. | ||
F | Colleges need better training and support on the proxy web service and overall workflow. | Improve the public documentation space for colleges with FAQs, video tutorials, support & training materials, and link to pre-seed student Accounts | ||
Implementation Plan | ||||
There is a comprehensive IT proxy integration process and most of the colleges have completed that work; however there has not been a clearly prescribed implementation plan or support materials developed to help colleges educate administrators and staff, nor materials for students (clear instructions, help). | Plan #1 - Update existing IT integration plan to include business operations students, faculty and staff ensuring that all CCC colleges (faculty, staff, Administrators, and students) understand the technical and operational implementation requirements; Work with colleges to ensure IdP is passing | |||
| ||||
| ||||
Communication Plan | ||||
A communication plan should include an Email campaign to all colleges, training & support materials, video tutorials for students and staff, implementation process & procedures, and process for support for colleges and students. | Descriptions of the OpenCCC Account, the CCCID, and the Proxy Diagrams showing how the OpenCCC and proxy workflows differ and how data flows across the full circle workflow. Provide summary of implementation options and link to detailed checklist on Public Documentation/Implementation site
| |||
effective implementation, training & support plan for all colleges as part of an "all college" communication (Email campaign & links to supporting docs online) with suggestions and alternatives for college implementation | ||||
UI/UX Design & Workflow Issues | ||||
UI Issues | ||||
A |
| |||
B |
| |||
C |
| |||
D |
| |||
UX Workflow Issues: | ||||
A |
| |||
B |
| |||
C |
| |||
D |
| |||
OpenCCC Account Issues: | ||||
A |
| |||
B |
| |||
Project Management Issues | ||||
A |
| |||
B |
| |||
C | ||||
Development & Deployment Issues | ||||
A |
| |||
B | ||||
C |