I've used a CustomLoginModule extending AbstractLoginModule with JAAS successfuly. See whether your jetty configuration files are updated to reflect the desired implementation.
In my case I had to update the element <Set name="UserRealms"> in jetty-jaas.xml to match the web.xml security-constraints.
Florin
vnamboo wrote:
Hi,
I am injecting my custom form authenticator class, which extends JETTY FormAuthenticator, to SecurityHandler using Spring. But I could see that my custom form authenticator's authenticate method is never triggered rather default FormAuthenticator is used.
Please advice why it is happening.