http://jira.jboss.com/jira/browse/SECURITY-236
With this change that came in 2.0.2.CR4, I have ensured that the client side SA usage
works as is. But yes, on the server side, SA usage should set the setServer flag.
But the server side usage of SA should by default have the server flag set due to the
JaasSecurityManagerService->startService()
| protected void startService() throws Exception
| {
| // use thread-local principal and credential propagation
| if (serverMode)
| SecurityAssociation.setServer();
|
I will take a look at the tests that you mention that are failing and see why this is an
issue.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160314#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...