Enhancing Authentication Security: CAS Implementation Guidelines and Benefits
This document outlines the requirements and benefits of utilizing Central Authentication Service (CAS) for web applications at the university. It details the daily authentication limits, the top 10 authenticating hosts, and emphasizes the necessity of CAS for accessing critical systems. The CAS RESTful web service and SSL/TLS client authentication ensure secure connections to ED-Auth. The transition timeline includes a target for Central IT applications by Fall 2012, with complete university application compliance forthcoming. For inquiries, reach out to middleware@vt.edu.
Enhancing Authentication Security: CAS Implementation Guidelines and Benefits
E N D
Presentation Transcript
Restricting ED-Auth Access 04.14.2011
Web Applications • Required to use CAS • http://www.middleware.vt.edu/doku.php?id=middleware:cas:client • Benefits of CAS • reduced liability • central location for communication • SSO
Other Applications • Required to use • CAS RESTful web service • http://www.middleware.vt.edu/doku.php?id=middleware:cas:restful or • SSL/TLS client authentication when connecting to ED-Auth • SASL bind not required
Timeline • Central IT applications by Fall 2012 • All university applications by ??
Questions? middleware@vt.edu www.middleware.vt.edu
