cas 3.0.0-beta1

Notable changes

• Drupal 11 compatibility (see "Updating to CAS 3.0" section below)
• Routes /cas and /caslogin are no longer accessible by logged in users. They will be redirected to the homepage instead of re-authenticating with CAS. See #3446948: Prevent access to cas.login route, if user is already logged in.

Updating to CAS 3.0

1. While still on Drupal 10, update your site to CAS 2.3.2. This is very important because starting with CAS 3.0.0, old (post)update functions are removed.
2. Require drupal/cas:^3.0 with Composer
3. If you have custom code that interacts with the CAS module, you may need to make some updates. There are some tiny backwards compatibility breaking changes that require your attention:
   • The type of value returned by CasLoginException::getCode() was changed from integer to enum of type CasLoginExceptionType. If your code calls this method, you should adapt. If you still need the integer value, you can do something like
     

     $codes = CasLoginExceptionType::cases();
     $code = array_search($exception->getCode(), $codes, TRUE);
     

   • The parameter of CasUserManager::getCasUsernameForAccount() is now strict typed as integer. Make sure you cast the parameter to an integer before is passed to the method:

     $account = ...;
     $uid = (int) $account->id();
     $name = \Drupal::service('cas.user_manager')->getCasUsernameForAccount($uid);
     

   • The CasServerConfig::setProtocolVersion() setter accepts now a CasProtocolVersion enum case as parameter instead of a string. Same, the CasServerConfig::getProtocolVersion() getter returns now a CasProtocolVersion enum case instead of a string. If needed, get the server version as a legacy string: CasServerConfig::getProtocolVersion()->value.
   • The CasServerConfig::setHttpScheme() setter accepts now a HttpScheme enum case as parameter instead of a string. Same, the CasServerConfig::getHttpScheme() getter returns now a HttpScheme enum case instead of a string. If needed, get the HTTP scheme as a legacy string: CasServerConfig:: getHttpScheme()->value.
   • The CasServerConfig::setVerify() setter accepts now a SslCertificateVerification enum case as parameter instead of an integer. Same, the CasServerConfig::getVerify() getter returns now a SslCertificateVerification enum case instead of an integer. If needed, get the certificate verification scheme as a legacy integer: CasServerConfig:: getVerify()->value.
4. You can now update your site to Drupal 11.
5. After updating to CAS 3.0, prepare for the next CAS version by replacing the deprecated code. Check #3462792: Some constants were deprecated and replaced with enums to learn what is deprecated in CAS 3.0 and adapt your code.

Issues in this release (compared from version 2.3.2):

• #3451262: Fix failures and enforce PHPStan, PHPCS & CSpell
• #3461478: Drupal 11 compatibility
• #3462684: Modernize CAS module code
• #3479696: Fix failing tests
• #3446948: Prevent access to cas.login route, if user is already logged in.