[jboss-user] [JBoss Seam] - Re: authenticator.authenticate called several times

2008-01-24 Thread terryb
Pete, I have resolved this issue now by implementing Identity based approach. For some reason, two posts have gone missing from this thread... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4122945#4122945 Reply to the post :

[jboss-user] [JBoss Seam] - Re: authenticator.authenticate called several times

2008-01-23 Thread [EMAIL PROTECTED]
Lets see the whole class MyAuthenticator View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4122696#4122696 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4122696 ___ jboss-user mailing

[jboss-user] [JBoss Seam] - Re: authenticator.authenticate called several times

2008-01-23 Thread terryb
I have removed some code for clarity. also this will change further as I use other Identity events. | MyAuthenticator.java | | | package au.edu.tisc.session; | | import org.jboss.seam.annotations.In; | import org.jboss.seam.annotations.Logger; | import

[jboss-user] [JBoss Seam] - Re: authenticator.authenticate called several times

2008-01-22 Thread appendix
Hi! I had same issue some time ago. Have a look at the following thread in this forum: http://www.jboss.com/index.html?module=bbop=viewtopict=122033 Cheers, K. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4122073#4122073 Reply to the post :

[jboss-user] [JBoss Seam] - Re: authenticator.authenticate called several times

2008-01-22 Thread terryb
Thanks you, I have upgraded seam 2.0.1CR1 and implementing security event approach to handle login pre/post processes. However, it appears that in my case identity.logout is not raising loggedOut event? I don't think I am supposed to do anything other than the code below to raise/capture

[jboss-user] [JBoss Seam] - Re: authenticator.authenticate called several times

2008-01-22 Thread nickarls
How about org.jboss.seam.loggedOut? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4122119#4122119 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4122119 ___ jboss-user mailing list

[jboss-user] [JBoss Seam] - Re: authenticator.authenticate called several times

2008-01-22 Thread [EMAIL PROTECTED]
It certainly should do. You can try placing a breakpoint on Identity.logout() and see if the event is raised correctly there. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4122185#4122185 Reply to the post :

[jboss-user] [JBoss Seam] - Re: authenticator.authenticate called several times

2008-01-22 Thread terryb
I tried org.jboss.seam.loggedOut and org.jboss.seam.security.loggedOut and also @Observer(Identity.EVENT_LOGGED_OUT) but no success. Pete, I used debugger and found that Identity.logout() does attempt to raise event but there is no event to be raise. Event.raiseEvent() method shows List

[jboss-user] [JBoss Seam] - Re: authenticator.authenticate called several times

2008-01-21 Thread msystems
Yes, I have the same problem ! When authenticate fails it is invoked two times - must be a bug? When authenticate is successful it is invoked one time. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4122046#4122046 Reply to the post :

[jboss-user] [JBoss Seam] - Re: authenticator.authenticate called several times

2008-01-21 Thread terryb
in my case, when authenticate fails it is invoked 3 times; and when authenticate is successful it is invokved 2 times. it seems like a bug, hopefully we get some reply on this soon. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4122047#4122047 Reply to the

[jboss-user] [JBoss Seam] - Re: authenticator.authenticate called several times

2008-01-21 Thread nickarls
There has been some threads on this and it's clarified in the 2.0.1CR1 manual: 13.4.2.2. Special Considerations When writing an authenticator method, it is important that it is kept minimal and free from any side-effects. This is because there is no guarantee as to how many times the