CAS Deprecated Environment: cas-deprecated

Owned by Baron Fujimoto
Last updated: Feb 26, 2024 by mhodges

 

Background

An interim and ephemeral CAS production environment, cas-deprecated.its.hawaii.edu, is deployed  for UH Login authentication whenever an upgrade is planned. This environment is deployed as a single instance and is not highly-available (HA).

This cas-deprecated environment provides an instance of the previous (older) version of CAS after CAS has been upgraded. It is made available for applications that have been found to be incompatible with the current (newer) version of CAS. It provides the application team more time to resolve compatibility issues with the current version of CAS. Application teams are strongly encourage to test their apps before upgrades, rather than after the fact.

CAS version information:

  • CAS version: 7.0

  • Deprecated CAS version: 6.6.12

Pending fixes to the affected applications' clients by their vendors, or in-house updates to the deployed IdP which may work around the client problems, applications have the option to use the idp-deprecated environment as an interim fallback workaround.

Deprecated CAS: current status

Available

Using the cas-deprecated environment (for SPs)

To use the the cas-deprecated environment, Service Providers (SP) will need to adjust their SSO configurations.

Generally, an SP will need to:

  • Change instances of "authn.hawaii.edu" to "cas-deprecated.its.hawaii.edu" in their configurations

If you would like to use an SP that is not already configured in our CAS production environment, we'll need to work together to add the integration for it to the cas-deprecated environment.

Troubleshooting

Please contact the IAM team at

It will facilitate troubleshooting if you can provide

  • A date/timestamp for the UH Login attempt

  • Username

  • Name of SP/application (even better if you have the SP's registered service URL)

  • A login URL for the SP that IAM staff may use to test

If you make it past the UH Login authentication process, but encounter errors from your SP

  • Applicable diagnostic logs from the SP

  • Tip: for our proof-of-concept SP, one tester had to close all their browser windows, and then re-open it before it worked

    • A new private/incognito window may have worked as well