As we have 5 nodes in CAPAM Prod, we are able to verify a Sybase target account from all CAPAM nodes except <hostname>. When we verify from <hostname> node, the verification fails and the account moves to unverified state. The same unverified account can be once again verified successfully from other nodes. This behavior is specific only to Sybase accounts in <hostname> node.
In the tomcat log we do see
Error Message: com.sybase.jdbc4.jdbc.SybDriver
Exception: com.cloakware.cspm.server.app.ApplicationException: com.sybase.jdbc4.jdbc.SybDriver
Stack Trace: com.cloakware.cspm.server.app.ApplicationException: com.sybase.jdbc4.jdbc.SybDriver
at com.cloakware.cspm.server.app.TargetManager.executeQuery(TargetManager.java:348)
at com.cloakware.cspm.server.plugin.targetmanager.SybaseTargetManager.verifyCredentials(SybaseTargetManager.java:132)
at com.cloakware.cspm.server.app.TargetManager.run(TargetManager.java:673)
Caused by: java.lang.ClassNotFoundException: com.sybase.jdbc4.jdbc.SybDriver
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1720)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at com.cloakware.cspm.server.app.TargetManager.executeQuery(TargetManager.java:344)
... 2 more
Release : 3.4 4.0
Component : sybase
The underlying error here is the error "Caused by: java.lang.ClassNotFoundException: com.sybase.jdbc4.jdbc.SybDriver"
Remove the existing file (if exists)
Restart PAM services from the gui
Add the appropriate version from the gui
Restart PAM services from the gui