Derived DataSourceUserManager.init() is called, but nothing else

Question

I'm trying to set up my application so that the UserManager class uses a class derived from DataSourceUserManager. I set up the properties that DataSourceUserManager needs, but I set the actual class to my own class.
It was a real pain to figure out exactly what file to put this in, as the various documents I've found that talk about this either list a different file name to use, or they don't specify exactly where the file is. In the case of JDeveloper, there seem to be several files that use the same "orion-application" dtd. Nevertheless, I think I might have found the correct file to put it in (by trial and error), which is "$JDEV_HOME/jdev/system/oc4j-config/application.xml". I say this because when I set a breakpoint on the "init()" method of my class, it actually hit it while starting up oc4j.
My problem is, outside of hitting the "init()" method, my class seemed to have no effect on the login validation process. None of the other methods in the class seemed to be executed (I set breakpoints on all the methods).
I'm still not quite sure exactly what methods I should put in my derived class. The methods in DataSourceUserManager don't match the "SimpleUserManager" class, so it doesn't look likely that adding "userExists()", "checkPassword()", and "inGroup()" would have any effect (unless something is using reflection to decide what methods to call, if any).
In my derived class, I just wrote derived versions of all the visible methods in DataSourceUserManager, and just called the base class method from the method, along with a print statement.
I set up my web application to use a secured area, and I verified that it goes to the login page when I request a protected page. When I attempt to login, I would assume that this is the point at which I should hit a breakpoint in one of the methods of my derived DSUM class. This didn't happen. It just sent me to my error page.
I would appreciate any information that would either solve my problem or help me track it better.

Answer 1

I haven't solved this, but I have found some more information, and I've tried a couple more things.
I finally noticed that there is javadoc for the orion api on the orionsupport site, so I found the javadoc for the DSUM class. This was helpful, as I then decided to write a subclass of "SimpleUserManager" that internally creates a DSUM object to delegate requests to. I then configured the appserver to use this new class instead of my other derived class, although with the same properties (since they're just getting piped to DSUM).
However, the result was identical. When the appserver started up, it hit the breakpoint in the "init()" method of my SimpleUserManager subclass. When I tried to log in to the application through my browser, it never hit the breakpoints in my other methods, and the web browser got sent my login error page.
For completeness, I'll include excerpts from my "web.xml" and "application.xml" (Orion's not J2EE's)with some paths elided, along with my "LoggingUserManager" class (minus package and imports).
----web.xml excerpt----
<security-constraint>
<web-resource-collection>
<web-resource-name>projname</web-resource-name>
<url-pattern>/main/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<role-name>analyst</role-name>
<role-name>administrator</role-name>
</auth-constraint>
<user-data-constraint>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
<login-config>
<auth-method>FORM</auth-method>
<realm-name>Projname</realm-name>
<form-login-config>
<form-login-page>/login/login.jsp</form-login-page>
<form-error-page>/login/error.jsp</form-error-page>
</form-login-config>
</login-config>
<security-role>
<description>A user allowed to make administrative changes</description>
<role-name>administrator</role-name>
</security-role>
<security-role>
<description>Data Analyst</description>
<role-name>analyst</role-name>
</security-role>
----web.xml excerpt----
----application.xml excerpt----
<user-manager class="....common.utils.LoggingUserManager">
<property name="table" value="UserProfileBean"/>
<property name="userNameField" value="userId"/>
<property name="passwordField" value="password"/>
<property name="dataSource" value="jdbc/OracleDS"/>
<property name="groupMembershipTableName" value="GroupMembershipBean"/>
<property name="groupMembershipGroupFieldName" value="groupName"/>
<property name="groupMembershipusernameFieldName" value="userId"/>
</user-manager>
<security-role-mapping name="administrator">
<group name="administrators"/>
</security-role-mapping>
<security-role-mapping name="analyst">
<group name="analysts"/>
</security-role-mapping>
<library path="...\oc4jConfig.jar"/>
----application.xml excerpt----
----LoggingUserManager.java----
public class LoggingUserManager extends SimpleUserManager
private DataSourceUserManager dataSourceUserManager =
new DataSourceUserManager();
public void init(Properties properties)
throws InstantiationException
dataSourceUserManager.init(properties);
protected boolean userExists(String userId)
com.evermind.security.User user =
dataSourceUserManager.getUser(userId);
boolean result = (user != null);
System.out.println("userExists. userId[" + userId +
"] result[" + result + "]");
return (result);
protected boolean checkPassword(String userId, String password)
com.evermind.security.User user =
dataSourceUserManager.getUser(userId);
boolean result = (user.authenticate(password));
System.out.println("checkPassword. userId[" + userId +
"] password[" + password +
"] result[" + result + "]");
return (result);
protected boolean inGroup(String userId, String groupName)
com.evermind.security.User user =
dataSourceUserManager.getUser(userId);
com.evermind.security.Group group =
dataSourceUserManager.getGroup(groupName);
boolean result = (user.isMemberOf(group));
System.out.println("inGroup. userId[" + userId +
"] groupName[" + groupName +
"] result[" + result + "]");
return (result);
----LoggingUserManager.java---- I still haven't resolved this, but I have made a little more progress.
I think I may have found the proper file to put the "<user-manager>" element into, which appears to be $JDEV_HOME/jdev/system/oc4j_config/application.xml.
Currently, this is what I have in that file:
<user-manager class="com.attws.it.bsa.felix.common.utils.LoggingUserManager">
<property name="table" value="UserProfileBean"/>
<property name="usernameField" value="userId"/>
<property name="passwordField" value="password"/>
<property name="dataSource" value="jdbc/OracleDS"/>
<property name="groupMembershipTableName" value="GroupMembershipBean"/>
<property name="groupMembershipGroupFieldName" value="groupName"/>
<property name="groupMembershipUsernameFieldName" value="userId"/>
<property name="staleness" value="0"/>
<property name="debug" value="99999"/>
</user-manager>
My "LoggingUserManager" class extends SimpleUserManger, but it creates an instance of DataSourceUserManager as an instance variable.
My "LoggingUserManager.init()" method looks like this:
public void init(Properties properties)
throws InstantiationException
for (Enumeration enum = properties.propertyNames();
enum.hasMoreElements(); ) {
String propertyName = (String) enum.nextElement();
System.out.println("property[" + propertyName + "] value[" +
properties.getProperty(propertyName) + "]");
new Throwable().printStackTrace();
dataSourceUserManager.init(properties);
When I debug the project in JDev, I hit my breakpoint in the "init()" method. When I get to the "dataSourceManager.init()" call, I step over it, and then I inspect the variables of the embedded dataSourceUserManager object. I see there is a "usernameField" attribute, and it's value is now "userId", which is correct. The other values also seem to be correct.
Then, I let the debugger continue executing to finish the server startup. Strangely, it hits the "init()" method breakpoint AGAIN. So I stepped through it again, and after stepping over the dsum.init() call, I inspected the variables again, and this time the "usernameField" attribute is "username". Note that I'm sending in the same properties values both times.
Then, I let the debugger continue to finish the server startup. I then go to my browser URL and try to authenticate. It hits my breakpoint in my "userExists" method, so I stepped through it. When it called "dataSourceUserManager.getUser()", it threw a SQLException, saying something about "USERNAME" being a bad identifier. I inspected the variables again at this point, and it still shows "usernameField" as being set to "username" (not terribly surprising).
So, at this point, I have no idea why it tried to call "init()" on my class twice, and why after the second time the DSUM variables were messed up. I also noticed that setting the "debug" flag to some value seemed to have no effect. This flag was documented in the javadoc for DSUM in the Orion API docs.