Tomcat Server Integration Verification

Delinea Driver Logs

Check the Tomcat server log to confirm whether your application uses the Delinea JDBC Proxy Driver. If your application uses the Delinea Proxy Driver, it will display the following log sequence:

  1. DelineaDriver: Driver register successfully
  2. DelineaDriver: Loading the property file of DelineaDriver
  3. DelineaDriverHelper: Driver configuration read successfully
  4. DelineaDriver: DB credential fetched successfully from Secret Server

Troubleshooting

  • The application account should have View Secret permission. The secret created in Secret Server should have application account permission.

  • Verify that the username and password of the secret is the same as your database name.

  • The Secret Server application account or the Delinea Platform service user should not be locked out.

  • SecretServer - getSecret: error=javax.net.ssl.SSLHandshakeException: com.ibm. jsse2.util.j: PKIX path building failed: com.ibm.security.cert.IBMCertPathBuilderException: unable to find valid certification path to requested target.

    Solution: Check your DelineaDriver.properties file trustAllCertificate parameter to see if it is false, set it as true. Setting it to true is not secure.

  • Check the error in SystemOut.log in C:\Program Files\Apache Software Foundation\Tomcat 10.0\logs.

    If you enter incorrect Secret Server or Delinea Platform credentials and fail to grant the user permission to access the secret, attempting to connect to your database will result in an error message in the SystemOut.log, stating "Access Denied" or "Authentication Failed".

  • If the following error occurs while running the SetupUtility. It means that the Tomcat service is running.
    alt

Tomcat catelina.log File Errors

The following are the solutions for errors that occur in the Tomcat catelina.log file.

  • DelineaDriver: Could not register the driver. Solution: Check all parameters in the DelineaDriver.properties file.

  • DelineaDriver: Unable to read the DelineaDriver.properties file.
    Solution: Check that the name of the file isDelineaDriver.properties and make sure the parameter is present in the configuration file.

  • DelineaDriver: URL is not valid. It must be started with jdbc:delinea.
    Solution: Check the connection string in the Java application configuration file.

    • For example, the SQL Server URL should be jdbc:sqlserver://localhost:1433;databaseName=onlinebookstore.
    • The JDBC Proxy URL should be jdbc:delinea:SSID:sqlserver://localhost:1433;databaseName=onlinebookstore.

  • SecretServer - getSecret: error getting secret, status:
    Solution: Check your Secret ID in the Java application configuration file. It should appear in front of the database username box.

  • Failed to get connection java.sql.SQLException: no suitable driver found.

    Solution: 1. Check whether the Tomcat lib folder contains the driver. 2. Check the driver in Tomcat and the Application lib folder, this might create a conflict. If both lib folders contain a driver, delete one of them. Preferably delete it from the Application lib folder.

    alt

  • You can change only the isLogging and LoginLevel parameters in the DelineaDriver.properties file manually. You must run SetupUtility.jar to change the other parameters (such as URL and identity), or the proxy driver will not work as expected.