I take a look at UsersRolesLoginModule.java
the loadProperties() method uses
Thread.currentThread().getContextClassLoader() to load
the properties files.
unfortunatly, it seems to pick the first available
when there are no files provided inside the package.
Any hints ?
ionel
__
I found the problem :
my service is deployed as a .sar file under the
server\default\deploy directory but the log shows this
:
2003-11-16 20:28:29,859 TRACE
[org.jboss.security.auth.login.XMLLoginConfigImpl]
getAppConfigurationEntry(ftp),
authInfo=AppConfigurationEntry[]:
[0]
LoginModule Class:
o
I noticed this as well, and found that the location of the
users.properties and roles.properties files needed to be in the
classpath of the deployed application, not in server\default\conf as
was previously the case. If I put then in WEB-INF\classes it worked
for my web application. This behavi
That is correct as far as shown. Turn on trace level logging for
the org.jboss.security package in the conf/log4j.xml config to
better see what is going on.
Scott Stark
Chief Technology Officer
JBoss Group, LLC
Ionel GARDAIS wrote:
Hi,
I'm experie
Hi,
I'm experiencing problems with UsersRolesLoginModule.
I added this to the
server\default\conf\login-config.xml file :
The users.properties and roles.properties files are
located in the same directory (server\default\conf)
and contain user/pass and user/roles properties as
usual.
Previously, we've talked about separating coding references from the
physical resources. This is fairly simple with an integrated
JBoss-Tomcat implementation. jboss-web.xml provides the mapping so that
ejb-ref-name -> jndi-name. However, how do you preserve that separation
when you are working with
