Thoughts about going from HttpServletRequest objcets to something we can feed to an AuthenticationHandler:
enters the
Logon controller applies an
Once the Logon Controller has applied its AuthenticationRequestBinder, it has an AuthenticationRequest in hand. It then passes that AuthenticationRequest to an AuthenticationHandler (or it passes it more generally into the CAS engine, which will return a TicketGrantingTicket, a Cookie representation of which the Logon Controller will then store back into the user's browser. The purpose of this page is to explore the path of the AuthenticationRequest more than to nail down exactly the Logon Controller implementation).
So the AuthenticationRequest is an argument to the AuthenticationHandler:
Our AuthenticationRequest has been transformed into an AuthenticationResult which CAS stores in the data associated with a GrantingTicket that it issues on the basis of this authentication.