Package net.unicon.cas.mfa.web.flow

Class Summary

Class	Description
AbstractMultiFactorAuthenticationViaFormAction	An abstraction that specifies how the authentication flow should behave.
CasMultiFactorWebflowConfigurer	Initialize the application context with the needed webflow mfa configuration as much as possible to simplify adding mfa into an existing overlay.
ConfigurableSpringWebflowExceptionHandler	A extension of TransitionExecutingFlowExecutionExceptionHandler that exposes configuration for convenience directly via a constructor, such that handlers can be configured via explicit spring beans.
GenerateMultiFactorCredentialsAction	An action to obtain/construct the MultiFactorCredentials instance and pass it along to the subsequent authentication flow.
InitiatingMultiFactorAuthenticationViaFormAction	The multifactor authentication service action that branches to an loa-defined subflow state based on the service loa requirement.
RemoveHostnameInContextAction	Check the context to see if the service available is the RemoveHostnameInContextAction.hostname.
SendTicketGrantingTicketAction	This is SendTicketGrantingTicketAction that mimics the default component in CAS with one key difference: it will only destroy the previous TGT issued if there is no MFA context available.
TerminatingMultiFactorAuthenticationViaFormAction	This is the final webflow action in the mfa authentication sequence that would ultimately issue the TGT and presents the "success" event.
ValidateInitialMultiFactorAuthenticationRequestAction	Determines whether the login flow needs to branch *now* to honor the authentication method requirements of If the Service expresses a requirement for how the user must authenticate, and there's an existing single sign-on session, and there is not a record in the user's single sign-on session of having already fulfilled that requirement, then fires the `requireMfa` event indicating that exceptional handling is required.

Exception Summary

Exception	Description
NoAuthenticationContextAvailable	In the event that a left-over TGT exists from previous session, from which an authentication context cannot be established, again, because the TGT is considered invalid, this exception will be thrown.