This week we were able to track down and resolve a logout issue with Canvas that has been frustrating users this spring. For many years Canvas has been using our legacy CAS authentication service for single-sign-on and single-sign-off. As more and more services have been moved to Microsoft’s Azure single-sign-on system, users have been making fewer login-requests to CAS that would normally push out the login session for 2 hours on each authentication. With Canvas as the only CAS-authenticated service that some users were accessing, they were finding that they would get logged out of after 2 hours when the CAS login session expired. We’ve changed the CAS configuration so that it will no longer logs users out of Canvas as part of single-sign-out. This will allow Canvas logins to remain active for up to 48 hours after the last Canvas page-load.
Separately, we address an issue that was preventing new course sections from flowing through from Banner to catalog.middlebury.edu and on to the Course Hub since May 7. Course sections are now flowing through nightly in time for summer program startup.
- Drupal embed 8.x-1.4
- Drupal file_browser 8.x-1.3
- Drupal htmlpurifier 8.x-1.0-rc2
- Drupal scheduler 8.x-1.2
- WordPress bbpress plugin 2.6.5
- WordPress instagram-feed plugin 2.4.3
- WordPress redirection plugin 4.8
- WordPress seriously-simple-podcasting plugin 2.2.0
- WordPress the-events-calendar plugin 5.1.2
- WordPress responsive theme 4.3.8
Fixes and Tweaks
- Canvas no longer participates in CAS single-sign-out, fixing an an issue where users were logged out after 2 hours.
- Put in a work-around for a Banner reporting-database error that was preventing course sections from flowing from Banner to catalog.middlebury.edu and on to the Course Hub since May 7. Course sections are now flowing through nightly.