# Package io.undertow.security.handlers

Class Summary
AbstractConfidentialityHandler: Handler responsible for checking of confidentiality is required for the requested resource and if so rejecting the request and redirecting to a secure address.
AbstractSecurityContextAssociationHandler: Base class responsible for associating the `SecurityContext` instance with the current request.
AuthenticationCallHandler: This is the final `HttpHandler` in the security chain, it's purpose is to act as a barrier at the end of the chain to ensure authenticate is called after the mechanisms have been associated with the context and the constraint checked.
AuthenticationConstraintHandler: Handler responsible for checking the constraints for the current request and marking authentication as required if applicable.
AuthenticationMechanismsHandler: Authentication handler that adds one or more authentication mechanisms to the security context
CachedAuthenticatedSessionHandler: `HttpHandler` responsible for setting up the `AuthenticatedSessionManager` for cached authentications and registering a `NotificationReceiver` to receive the security notifications.
NotificationReceiverHandler: A `HttpHandler` to register a list of `NotificationReceiver` instances with the current `SecurityContext`.
SecurityInitialHandler: The security handler responsible for attaching the SecurityContext to the current `HttpServerExchange`.
SinglePortConfidentialityHandler: An extension to `AbstractConfidentialityHandler` that uses the Host header from the incoming message and specifies the confidential address by just switching the port.