Hello,
I have the same problem getting the exact exception cause on the client side.
If you are lucky your client will run on the same VM that the logincontext
does. In that case you might use
Object exception =
org.jboss.security.SecurityAssociation.getContextInfo("org.jboss.security.excepti
Add a custom interceptor that changes the SecurityException to the exception
thrown from the login module as obtained from the
SecurityAssociation.getContext().
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858451#3858451
Reply to the post :
http://www.jb
You have to parse the stack of incoming exceptions, beggining with the remote
exception. In addition you can substitute the default security interceptor with
your own, which will throw more detailed exceptions...
Alexander
View the original post :
http://www.jboss.org/index.html?module=bb&op=v
I found some infos in this thread:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=57240
but unfortunately not really helpfull.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858327#3858327
Reply to the post :
http://www.jboss.org/index.html?module=
