I was acutally able to work around the "principal=null" condition by setting
the following property on my Login Module:
<application-policy name = "nms">
| <authentication>
| <login-module code =
"org.jboss.security.auth.spi.DatabaseServerLoginModule"
| flag = "required">
| <module-option name="dsJndiName">java:/NMS-DS</module-option>
| <module-option name = "hashAlgorithm">MD5</module-option>
| <module-option name = "hashEncoding">base64</module-option>
| <module-option
name="unauthenticatedIdentity">nobody</module-option>
| </login-module>
| </authentication>
| </application-policy>
This causes the principal for unauthenticated entities (such as MDBs or MBeans)
to be "nobody". Pair this with a <run-as> and you can kind of get MDB's to
interact properly with secure session beans.
Unfortunatley, having a principal on the call does not fix my problem where
isCallerInRole is returning an unexpected result.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867130#3867130
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867130
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
