Problem w/ using DBTableOraDataSourceLoginModule w/ JDEV

Question

I am using JDeveloper 10.1.3.2 and have configured security to use the DBTableOraDataSourceLoginModule. I receive the following message when I attempt to login via a form, so it looks like the RealmLogin is still being used instead of the DB. I have configured the application.xml and system-jazn-data.xml per Oracle's instructions. Any comments or suggestions? My system-jazn entry is below. Thanks.
javax.security.auth.login.LoginException: User [ABCDEF] does not exist in system.
     at oracle.security.jazn.login.module.RealmLoginModule.authenticate(RealmLoginModule.java:113)
     at oracle.security.jazn.login.module.RealmLoginModule.authenticate(RealmLoginModule.java:86)
     at oracle.security.jazn.login.module.AbstractLoginModule.login(AbstractLoginModule.java:265)
<jazn-loginconfig>
     <application>
          <name>Prototype</name>
<login-module>
<class>
oracle.security.jazn.login.module.db.DBTableOraDataSourceLoginModule
</class>
<control-flag>required</control-flag>
<options>
<option>
<name>data_source_name</name>
<value>jdbc/devdata</value>
</option>
<option>
<name>table</name>
<value>USERS</value>
</option>
<option>
<name>roles_fk_column</name>
<value>GROUP_ID</value>
</option>
<option>
<name>groupMembershipGroupFieldName</name>
<value>GROUP_J2EE</value>
</option>
<option>
<name>user_pk_column</name>
<value>USER_ID</value>
</option>
<option>
<name>passwordField</name>
<value>PASSWD</value>
</option>
<option>
<name>groupMembershipTableName</name>
<value>USER_GROUP</value>
</option>
<option>
<name>usernameField</name>
<value>LOGIN</value>
</option>
<option>
<name>casing</name>
<value>toupper</value>
</option>
</options>
</login-module>
     </application>

Answer 1

First, turn up your logging in your j2ee-logging.xml to be TRACE:32 instead of NOTIFICATION:1. This will allow you to see in more detail what is going on during the authentication stage.
Typically, when u are running into problems with the DB Login module it is the connectivity to it.
1) First, go into EM and check the Datasource and connection pool configured for the DB Table login module. There is a function within this screen to test the connection. Try doing a select from the tables you defined for your users and groups.
2) Look in your custom security provider settings and make sure:
a. You are specifying the correct jdbc namespace for the datasource
b. That you didn't misspell the any of the table settings.
I think you mentioned a 401 error, which is authorization error. So, most likely your DBTable is working correctly. Make sure that you specified your roles correctly in your web.xml and your role mapping in orion-application.xml
For example, in your orion-application.xml:
security-role-mapping name="sr_developer">
<group name="developers" />
</security-role-mapping>
<security-role-mapping name="sr_manager">
<group name="managers" />
</security-role-mapping>
<jazn provider="XML">
<property name="custom.loginmodule.provider" value="true"/>
     <property name="role.mapping.dynamic" value="true"/>
<property name="role.compare.ignorecase" value="true"/>
</jazn>
In your web.xml:
web-app>
<display-name>Simple Servlet for testing Custom Provider</display-name>
<distributable />
<servlet>
<servlet-name>SimpleServlet</servlet-name>
<description>Servlet retrieves remote user info</description>
<servlet-class>SimpleServlet</servlet-class>
<!-- role name used in code -->
<security-role-ref>
<role-name>ar_developer</role-name>
<role-link>sr_developer</role-link>
</security-role-ref>
<security-role-ref>
     <role-name>ar_manager</role-name>
     <role-link>sr_manager</role-link>
</security-role-ref>
</servlet>
<servlet-mapping>
<servlet-name>SimpleServlet</servlet-name>
<url-pattern>/protectedA</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>SimpleServlet</servlet-name>
<url-pattern>/protectedB</url-pattern>
</servlet-mapping>
<security-role>
<role-name>sr_developer</role-name>
</security-role>
<security-role>
     <role-name>sr_manager</role-name>
</security-role>
<!-- security constraints -->
<security-constraint>
<web-resource-collection>
<web-resource-name>protectedA</web-resource-name>
<url-pattern>/protectedA</url-pattern>
</web-resource-collection>
<!-- authorization -->
<auth-constraint>
<role-name>sr_developer</role-name>
</auth-constraint>
</security-constraint>
<security-constraint>
<web-resource-collection>
<web-resource-name>protectedB</web-resource-name>
<url-pattern>/protectedB</url-pattern>
</web-resource-collection>
<!-- authorization -->
<auth-constraint>
<role-name>sr_manager</role-name>
</auth-constraint>
</security-constraint>