When Using Custom Credential Mapper, WebLogic Startup Fails to Create the Connection Pool
(Doc ID 1996913.1)
Last updated on JUNE 10, 2022
Applies to:Oracle WebLogic Server - Version 10.3.5 and later
Information in this document applies to any platform.
When using a credential mapper to integrate with WebLogic's "identity based connection pooling" feature, if a data source connection is created, the credentials provided by the credential mapper module are used, which means that the credentials configured on the data source are not relevant and can be obsolete (incorrect password). A patch was provided that lets JDBC retrieve the password when using a custom credential mapper and when identity pooling is enabled. See JDBC doesn't Retrieve Password When Using a Custom Credential Mapper and "Enable Identity Pooling" Note 1541375.1.
However, during WebLogic startup, with Initial Capacity > 0, the credential mapper is not invoked and the credentials configured on the data source are always used. This will fail, because the password is incorrect, and the data source will not be deployed to the target server, which means that data source will be unusable for applications.
The following error is received with Initial Capacity > 0:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document