The following issues started to occur with OracleDB users.
1. Unable to vault database accounts and synchronize in PAM
2. Unable to verify a few of the existing accounts, it accepts the password, shows unverified
Tomcat catalina.out reports following exception:
java.sql.SQLException: ORA-01005: null password given; logon denied
It is a known issue with Oracle JDBC Driver verion 184.108.40.206
Release : 3.x.x
Component : PRIVILEGED ACCESS MANAGEMENT
PAM bundles Oracle JDBC Driver 220.127.116.11 which is affected by a known issue when FIPS mode is enabled.
This issue is even observed without FIPS enabled.
When using the FIPS, the JDBC driver may report an ORA-01005 error when opening a connection.
This issue is reported in Bug 25034560 - 18.104.22.168 JDBC WITH BOUNCYCASTLE FIPS FAILS WITH ORA-1005, closed as
duplicate of unpublished Bug 26371973 - UNABLE TO CONNECT TO ORACLE DATABASE WHEN FIPS140-2 IS ENABLED.
Apply Merge Patch: 26675580 on top of JDBC 22.214.171.124.
Merge Patch:26675494 also exists for JDBC 126.96.36.199.
As a workaround for this issue, use JDBC 188.8.131.52.0 instead of JDBC 184.108.40.206.0 as this issue has been determined in some
cases not to be reproducible with JDBC 220.127.116.11.0 .
BUG:25034560 - 18.104.22.168 JDBC WITH BOUNCYCASTLE FIPS FAILS WITH ORA-1005; 22.214.171.124 WORKS
This issue can be encountered if PAM servers or OracleDB has FIPS mode enabled.
This ojdbc7-126.96.36.199.jar needs to be replaced with ojdbc7-188.8.131.52.jar(older) or ojdbc7-184.108.40.206.jar(newer) to avoid this problem.