Yep. The principal is not stored in the session, so replicating the session
doesn't propagate it around the cluster. Using ClusteredSingleSignOn works
around the problem.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234815#4234815
Reply to the post :
http
Fixed it.
Enabling "ClusteredSingleSign" did the trick.
Enabling this replicating the principal on second node correctly.
Thanks,
Suresh
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232529#4232529
Reply to the post :
http://www.jboss.org/index.html?modul
Further debugging, I found the issue is related to JAAS authentication at the
application level.
On failover the user principal is reset to null on second node hence, I can;t
access the secured resources.
My expectation is as I logged into application on node1 (user principal is set
correctly)..
Please ignore this...
I was wrong with my analysis. seems spring + dwr layer is not problematic.
Anyway, I still have the problem unresolved... will post the details, once I
get the fail-over working fine.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232499
