Downloads
Release notes
We are proud to announce the first beta release in the 6.x-3.0 branch. Please back up your database before upgrading.
Changes since 6.x-2.x
(Important) Database Schema Changes
Previous versions of CAS used the {authmap} table to store the relationship between CAS usernames and Drupal users. This was changed to use our own table {cas_user} to prevent conflicts with authnames shared between different external authentication modules. If you were sharing the {authmap} and {users} table between different Drupal installations, you may need to update your configuration to also share the {cas_user} table as well.
Upgrade routines have been provided. It is not possible to revert to CAS 6.x-2.x after upgrading. Please back up your database.
(Important) Login Link Changes
In previous versions of CAS, logins could be triggered by creating a link to cas which (after login) would automatically redirect back to the referring page. Now the login destination must be specified explicitly (instead of relying on the HTTP Referrer) --- for example cas?destination=node/2.
If you include a link to /cas in your theme, you may need to replace the code with something like
print l(t('Log in'), 'cas', array('query' => drupal_get_destination()));
Upgrading
phpCAS version 1.0.0 or later is required, however version 1.1.3 or later is highly recommended for security.
New Features
- Simpler configuration interface.
- Single Sign-Out is always enabled.
- CAS username(s) associated with an account may be edited.
- New ability to directly add CAS users.
- First login destination works for admin created accounts.
- Automated test routines.
- More robust login redirection.
- installation documentation.
- A documented API for other modules -- see cas.api.php.
Changes since 6.x-3.0-alpha1
- Token support.
hook_cas_user_presave()changed slightly -- see cas.api.php- Improved login form compatibility with Rubik based themes (e.g., OpenAtrium)
