Iit seems to me or there is no way to set up acegi with an
account blocker that is called after a specified number of consecutive failed
authentication (not authorization) attemps for the same username?
You can write and register a custom ApplicationListener, then check for theauthentication failure event... you can do something to update the failed logon attempts, then on subsequent logon attempts you will probably have to check the logon attempts count something like that.
Acegi does not
Hi,I've created custom components to bring Acegi support to the JSF Framework. I've mapped Acegi's JSP tags authorize and authentication to JSF as components.The usage is same as the jsp tags, you can find more information (download, usage etc.) on my blog at;
That is actually just an overly verbose DEBUG statement if you look.
If your Siteminder integration is actually working I would turn off
DEBUG SecurityEnforcementFilter in log4j.
On 1/19/06, Garvey, Paul M (GE Commercial Finance) [EMAIL PROTECTED] wrote:
Help!,
I am having a hard time
I'm not using JSF, but this sounds pretty cool, so I'll bump it for
other's attention :-)ScottQuoting Cagatay Civici
[EMAIL PROTECTED]: Hi, I've
created custom components to bring Acegi support to the JSF Framework. I've mapped Acegi's JSP tags authorize and authentication to JSF as components.
I am not able to get acegi to work with Siteminder so I turned on debug
mode.
But if I do a request.getHeader(HRID) from my index.jsp I am able to
display my username.
However, acegi spits out the credential not found exception way before
it even get to the
loadUserByUsername(username) in the
