Table of Contents
Advertisement
Chapter 6: Authentication Using External Servers
You may be prompted to restart the BSC. We recommend that you do not restart the BSC
until you have completely finished configuring the BSC for use in your network.
CAS Authentication
The Central Authentication Server (CAS) is designed as a standalone web application to:
facilitate single sign-on across multiple web applications and core services that aren't
necessarily web-based but have a web front end, provide trusted and untrusted services,
authenticate users without having access to their passwords, simplify procedures that
applications must follow to perform authentication, and localize actual ("primary")
authentication to a single web application.
The Central Authentication Server (CAS) is designed as a standalone web application. It
is currently implemented as several Java servlets and runs through an HTTPS server. It is
accessed through three URLs, the login URL, the validation URL, and the optional logout
URL.
To use the central authentication service, an application redirects its users, or simply
creates a hyperlink, to the login URL. If authentication is successful, the CAS creates a
long, random number, called a "ticket." It then associates this ticket with the user who
successfully authenticated and the service to which the user was trying to authenticate.
6-30
Figure 6-12: New CAS Server Page
Advertisement
Table of Contents
