This data is available in the Authentication object, but this component follows the `AuthenticationMetaDataPopulator` paradigm for injecting arbitrary attributes into the ticket validation `Assertion` and subsequently the protocol response. I can imagine we would use this component by default with the CAS 3.0 protocol to provide the client with the handler names that authenticated credentials.