I have tried a lot of things to fix this issue
And what I discovered is the following...
Even the simpliest thing jGuardExample.war kills any embedded jboss security...
For example, jmx-console, it can be set-up to allow only "admin"-users via
standard http auth...
And if we copy jGuardExa
Settings for "queue/A" and "QueueConnectionFactory" are default settings
coming with jboss 4.0.3
*** jboss.xml ***
ReplicationMDBBean
queue/A
** ejb-jar.xml***
http://java.sun.com/dtd/ejb-jar_2_0
Give details on the security config of your MDB.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3946981#3946981
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3946981
Yes, I can see the difference...
I even understand that it sounds stupid :)
But the point is...
When I comment out jGuar's "filter" and "filter-mapping" from my web.xml, I
have my MDB working well.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3946955#3946955
JGuard works by adding their net.sf.jguard.filters.AccessFilter version of a
javax.servlet.Filter to your web application. As such it is separate from
container managed security. Do you see the difference?
cgriffith
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewto
