"bossman" wrote : Add "unauthenticatedIdentity" module option as in...
|
|
|
|
| JMSReceiver
|
| ManageMDBRole,ManageDeviceRegistrationManagerRole,ManageGatewayManagementRole
|
| JMSReceiver
|
|
|
|
What is that option suppo
Add "unauthenticatedIdentity" module option as in...
JMSReceiver
ManageMDBRole,ManageDeviceRegistrationManagerRole,ManageGatewayManagementRole
JMSReceiver
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=
I'm still wrestling with my security problems (2 weeks now) and I still can't find the
solution (other than sticking with WebLogic). I've tried using the
stuff, but that doesn't seem to be helping. Let me provide more detail.
I've got a MDB that listens on a particular queue and, when process
jboss-3.2 uses a different notion of the run-as role. It is the ONLY role assumed by
the caller, it is not the name of the principal to which roles are assigned.
|
|
| ManageGatewayManagementRole
|
|
|
or role-name could be ManageDeviceRegistrationManagerRole depe
I *think* you have to add
yourprincipalthathastherightroles
to the MDB in your jboss.xml.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3849435#3849435
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3849435
-
Whoops, clicked the wrong button...
I'm in the process of porting over a WebLogic-based application over to JBoss, and the
security aspects are giving me an incredible headache. One of the big problems I'm
having is in getting a MDB to run with a principal identity.
I've got the following entr
