CAS to replace AWS
Many applications on campus which require CalNet authentication use the Authentication Web Server (AWS) service; examples include AirBears, blu, and a number of applications deployed by departments, including the content management systems developed by LSCR’s web team.
Due to the aging of the technology, AWS is going to be replaced by Central Authentication Service (CAS); the tentative date for the deprecation of AWS is December 31, 2008. Moving from AWS to CAS will require some changes to all the applications currently using AWS; the changes should be fairly simple to implement.
The biggest advantage of CAS is that it provides single sign-on to all applications using CAS; that is, once you’ve logged on through CAS once, if you visit another web site which uses CAS, you won’t have to retype your password. This will be a boon for most users, especially those coming in through AirBears who’ll have to use CAS to get on the network in the first place.
If you have an application that’s currently using AWS, you should look at the links above to start working on migrating to CAS. Both services will run in parallel for at least the rest of this year; you can move to CAS at any time. It probably makes sense to move sooner rather than later, since CAS provides better functionality.
