Thanks for your reply Scott.
Had tried to explicity specify the user and roles file in the application
policy. however it didn't make a difference.
The problem ended up being the ClientLoginModule that was included in my
application policy. i.e.
Before:
<application-policy name = "esubmit">
<login-module code="org.jboss.security.ClientLoginModule" flag="required">
</login-module>
<login-module code = "org.jboss.security.auth.spi.UsersRolesLoginModule"
flag = "required">
<module-option name="unauthenticatedIdentity">nobody</module-option>
<module-option name="usersProperties">users.properties</module-option>
<module-option name="rolesProperties">roles.properties</module-option>
</login-module>
</application-policy>
After:
<application-policy name = "esubmit">
<login-module code = "org.jboss.security.auth.spi.UsersRolesLoginModule"
flag = "required">
<module-option name="unauthenticatedIdentity">nobody</module-option>
<module-option name="usersProperties">users.properties</module-option>
<module-option name="rolesProperties">roles.properties</module-option>
</login-module>
</application-policy>
This rectified the problem in both jboss 4.0 and jboss 4.0.1RC1.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854368#3854368
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3854368
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
