Verification

Delinea Credentials Cache is used in several JDBC Proxy Driver integrations. Prior to verifying Delinea Credentials Cache, make sure that the following JDBC Proxy Driver integrations are installed and configured:

Verifying Delinea Credentials Cache in Apache Tomcat

To ensure that your application configured in Apache Tomcat uses Delinea Credentials Cache, you need to check the logs. The procedure below provides an example of verifying that a Student JPA application configured in Apache Tomcat uses Delinea Credentials Cache.

  1. Open the Command Prompt window and navigate to the folder containing the utlity.jar file.

  2. Run the SetUpUtility.jar file to set the Delinea JDBC Proxy Driver.

  3. Enter the details of Secret Server, the username of the Secret Server application account, and the password of the application account.

  4. Enter the path of the application's lib folder.

  5. Specify whether to use Delinea Credentials Cache:

    • To confirm the use of Delinea Credentials Cache, enter y at a command prompt .

    • To specify that the application configured on Apache Tomcat will not use Delinea Credentials Cache, enter n.

  6. On your computer, open the Delinea Credentials Cache folder.

  7. In the folder, open the appsetting.json file and set CredCacheExpirationInMinutes (the cache expiration period) to 10.

    8. By default, the Secret View Interval Minutes setting is set to 5 minutes in Secret Server. You can change the cache expiration period in the configuration of your Secret Server account.

  8. On your computer, open the folder where Apache Tomcat is configured.

  9. Open the DelineaDriver.properties file.

  10. Check that the useDelineaCache=y parameter is set in the DelineaDriver.properties file.

  11. Open the application configured in Apache Tomcat.

  12. Enter the value for the book parameter or student parameter.

  13. Check in the Apache Tomcat logs that the connection is made through Delinea Credentials Cache.

Verifying Delinea Credentials Cache in WebSphere

  1. In WebSphere, set up the Student JPA application and provide the example settings shown in the screenshot below in the persistent.xml file.

  2. Open the DelineaDriver.properties file.

  3. Check that the useDelineaCache=y parameter is set in the DelineaDriver.properties file.

  4. Open the Student JPA application configured in WebSphere.

  5. Enter the value for the book or student parameter.

  6. Check in the WebSphere logs that the connection is made through Delinea Credentials Cache.

Verifying Delinea Credentials Cache with MID Server Integrations

When using a MID Server (such as a ServiceNow MID Server) with Delinea Platform or Secret Server, credentials can be retrieved through the Delinea Credential Cache.

To verify that the Credential Cache is functioning correctly in a MID Server integration:

  1. Confirm that the MID Server is configured with a Delinea Credential Resolver (for either Secret Server or Delinea Platform).

  2. Confirm that MID Server is configured with Delinea credential cache. Follow this link to see how to enable Delinea Credential Cache.

  3. In your integration platform, run a test credential retrieval or connection test.

    • If the connection is successful and no direct credential prompt occurs, the MID Server is retrieving credentials from the configured cache.

  4. In Secret Server or the Delinea Platform, review the wrapper.log file of the MID  Server to confirm that the MID Server host has requested credentials through the cache.

  5. If the credential request does not appear in the wrapper.log file logs, review the MID Server configuration to ensure caching is enabled.