Error While Authentication When Using SQLReadOnlyAuthenticatior Provider

Question

All,
I am trying to setup a sql read only authentication provider, but after restart weblogic i can't authenticate any user inserted into database tables and when I try to list all user and groups using admin console i got the following exception.
Caused by: java.sql.SQLException: [Security:090788]"Problem with DataSource/ConnectionPool configuration, verify DataSource name jdbc/sisad is correct and Pool configurations are correct"
at weblogic.security.providers.authentication.DBMSDatabaseConnectionPoolImpl.getRawConnection(DBMSDatabaseConnectionPoolImpl.java:136)
at weblogic.security.providers.authentication.DBMSSQLReadOnlyDatabaseConnectionPoolImpl.checkoutConnection(DBMSSQLReadOnlyDatabaseConnectionPoolImpl.java:26)
at weblogic.security.providers.authentication.DBMSSQLReadOnlyAuthenticatorDelegateImpl.getReadOnlyConnection(DBMSSQLReadOnlyAuthenticatorDelegateImpl.java:571)
at weblogic.security.providers.authentication.DBMSSQLReadOnlyAuthenticatorDelegateImpl.listGroups(DBMSSQLReadOnlyAuthenticatorDelegateImpl.java:429)
... 115 more
I double checked the datasource and i can test it using admin server console. Please, check my setup . Any help is appreciated. I am using weblogic 10.3.3 and redhat 5.2
security provider fragment from config.xml
<sec:authentication-provider xsi:type="wls:read-only-sql-authenticatorType">
<sec:name>SisadSQLAuthenticator</sec:name>
<sec:control-flag>SUFFICIENT</sec:control-flag>
<wls:data-source-name>jdbc/sisad</wls:data-source-name>
<wls:plaintext-passwords-enabled>true</wls:plaintext-passwords-enabled>
<wls:descriptions-supported>false</wls:descriptions-supported>
<wls:sql-get-users-password>SELECT TX_SENHA FROM TBL_USUARIO_SISAD WHERE TX_MATRICULA_SIAPE = ?</wls:sql-get-users-password>
<wls:sql-user-exists>SELECT TX_MATRICULA_SIAPE FROM TBL_USUARIO_SISAD WHERE TX_MATRICULA_SIAPE LIKE ?</wls:sql-user-exists>
<wls:sql-list-member-groups>SELECT LO_PERFIL FROM TBL_USUARIO_SISAD WHERE TX_MATRICULA_SIAPE = ?</wls:sql-list-member-groups>
<wls:sql-list-users>SELECT TX_MATRICULA_SIAPE FROM TBL_USUARIO_SISAD WHERE TX_MATRICULA_SIAPE LIKE ?</wls:sql-list-users>
<wls:sql-list-groups>SELECT DISTINCT LO_PERFIL FROM TBL_USUARIO_SISAD WHERE LO_PERFIL LIKE ?</wls:sql-list-groups>
<wls:sql-group-exists>SELECT DISTINCT LO_PERFIL FROM TBL_USUARIO_SISAD WHERE LO_PERFIL = ?</wls:sql-group-exists>
<wls:sql-is-member>SELECT TX_MATRICULA_SISAD FROM TBL_USUARIO_SISAD WHERE LO_PERFIL = ? AND TX_MATRICULA_SISAD = ?</wls:sql-is-member>
</sec:authentication-provider>
data source fragment from config.xml
<jdbc-system-resource>
<name>sisad</name>
<target>AdminServer,soa_server1</target>
<descriptor-file-name>jdbc/sisad-jdbc.xml</descriptor-file-name>
</jdbc-system-resource>
sisda-jdbc.xml
<?xml version='1.0' encoding='UTF-8'?>
<jdbc-data-source xmlns="http://xmlns.oracle.com/weblogic/jdbc-data-source" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/jdbc-data-source http://xmlns.oracle.com/weblogic/jdbc-data-source/1.0/jdbc-data-source.xsd">
<name>sisad</name>
<jdbc-driver-params>
<url>jdbc:oracle:thin:@10.60.2.27:1521:desenv1</url>
<driver-name>oracle.jdbc.xa.client.OracleXADataSource</driver-name>
<properties>
<property>
<name>user</name>
<value>sisad</value>
</property>
</properties>
<password-encrypted>{AES}OOQB+cwv7I9dBeq2712AG7jm3O4+WiAjvtR4f3dvuqg=</password-encrypted>
</jdbc-driver-params>
<jdbc-connection-pool-params>
<test-table-name>SQL SELECT 1 FROM DUAL</test-table-name>
</jdbc-connection-pool-params>
<jdbc-data-source-params>
<jndi-name>jdbc/sisad</jndi-name>
<global-transactions-protocol>TwoPhaseCommit</global-transactions-protocol>
</jdbc-data-source-params>
</jdbc-data-source>

Answer 1

All,
I just figured out the problem. Actually the datasource name parameter in the read only sql authenticator provider must be the weblogic datasource name not the jdni datasource alias. in my case i must use sisad not jdbc/sisad. my fault.
Edited by: aviana on Mar 17, 2011 5:06 PM