JNDI Data Source Authentication

Question

Why doesn't the following work?
public void getConnection(String dbuser, String dbpass) throws SQLException, NamingException {
Context context = new InitialContext();
DataSource ds = (DataSource)context.lookup(DATA_SOURCE_NAME);
return ds.getConnection(dbuser,dbpass);
It seems like this authenticates against the WebLogic security realm, and not the database (which is what the Java API specifies). Is this supposed to be the case? How can I work around this so that SQL calls are made in the dbuser's name and not the credentials I supplied for the Data Source?
Message was edited by:
bernerbits

Answer 1

Derek Berner wrote:
Why doesn't the following work?
public void getConnection(String dbuser, String dbpass) throws SQLException, NamingException {
Context context = new InitialContext();
DataSource ds = (DataSource)context.lookup(DATA_SOURCE_NAME);
return ds.getConnection(dbuser,dbpass);
It seems like this authenticates against the WebLogic security realm, and not the database
(which is what the Java API specifies). Is this supposed to be the case? How can I work
around this so that SQL calls are made in the dbuser's name and not the credentials I supplied for the Data Source?
Message was edited by:
bernerbitsHi. This is running as designed. The DataSource to a WebLogic JDBC connection
pool will be delivering one of the identically-made already existing connections
in the pool. As such the typical call is the no-argument getConnection() call.
We do implement weblogic security with the user/password form.
If you want a JDBC connection with a named user/password, you should
either have a pool with such ( and use the no-argument call) or you must
make a non-pooled direct connection. Note that you can have as many pools
as you want, each perhaps with only one connection, and you can dynamically
create pools.
For an upcoming release of WLS we will offer heterogenous (multiple DBMS
user) pools.
Joe