Issues & Concerns:
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 | Proposed Solutions | |||
A |
|
| ||
| ||||
| ||||
| ||||
Proxy Perception Issues | Proposed Solutions | |||
Colleges do not understand the underlying purpose of the proxy, or the importance of the OpenCCC Account and the CCCID. | Tech Center needs to implement an effective implementation process for the proxy to send out communication to all colleges with a consist | |||
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 | ||||
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.. | ||||
Colleges perceive the proxy as a barrier for their students | ||||
Faculty and staff perceive the proxy as a barrier for them - they are frustrated | ||||
Colleges need better training and support on the proxy web service and overall workflow. | ||||
UI/UX Design & Workflow Issues | Proposed Solutions | |||
UI Issues: The proxy sign-in page needs a better design to legitimize the service for students and colleges. | ||||
The sign-in page lacks legitimate, recognizable branding to the user so they feel comfortable that the re-direct is official and approved by the college, the CCCCO, and the application they are trying to access. | ||||
The sign-in page messaging is confusing for the user; it's not clear what login credentials we are asking for. The student has just signed in to their college IdP and then immediately we are redirecting them to a second, different sign in page. The messaging lacks enough information to explain why the student is seeing the proxy sign-in page. | ||||
The sign-in page needs a Help link or better, an embedded video tutorial that can guide the student through the process (either sign-in with OpenCCC credentials, or recover account credentials and sign-in, or create an account if you don't have one. | ||||
UX Workflow Issues: To streamline the proxy workflow, colleges want a "short-form" OpenCCC Account creation process for the students who are already students at a college. | ||||
Colleges are frustrated that students are re-directed to the proxy while they to complete assignments for a course or program. Colleges want an optional workflow process that doesn't interrupt their students on their way to an important are trying to access a systemwide application | ||||
Colleges are frustrated that we don't offer an easy way for bulk assignment of CCCID numbers to non-credit or special needs students (Adult Ed, Inmates, special K12 programs, and non-credit students). Colleges want to provide the Tech Center with a spreadsheet of account data and get back bulk-assigned CCCID assignment process | ||||
Many colleges don't know how to get the CCCIDs created during proxy re-direct back into their SIS or common directory systems. Better, comprehensive Information needs to be provided to colleges about the EPPN>CCCID API process. | ||||
OpenCCC Account Issues: | ||||
Overall, the OpenCCC Account Creation process, especially when asked during proxy re-direct, is perceived as redundant, unnecessary, long and intrusive; especially when the user has already provided most of the information to the college already when they applied, enrolled, registered, etc. | ||||
Students are put off by the questions, especially SSN, Birthdate, address, phone, email, etc. | ||||
Project Management Issues | Proposed Solutions | |||
It is very unclear whether the SSO proxy is a product or a required technology component or simply a system technical requirement - both internally and externally from the field. | ||||
Currently the SSO proxy does not have a project charter, project plan, business requirements, or roadmap; thus making it extremely difficult for continuous improvement and supporting our colleges. | ||||
Development & Deployment Issues | Proposed Solutions | |||
The SSO Proxy also lacks a clear development team and | ||||
General Observations:
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. These are colleges are:
- Antelope Valley College
- Butte College