Frequently Asked Questions

Check the integration debugging log for the specific error. Common causes are:

• The Delinea Secret Server authentication method does not have an access role that grants read access to the specified secret.

• For rotated secrets, the Secret Type is set to static (or vice versa), causing the wrong API endpoint to be called.

• The wrong API key or username/password combination might have been entered.

• The Delinea Secret Server host is unreachable from the scanner (firewall, incorrect hostname, or port).

• If using a self-hosted gateway, verify the SSL certificate of the gateway is trusted by the scanner, or consider testing with Verify SSL disabled.

• Verify that the duration of the scan did not surpass the token expiration time by reviewing the expiration details of the Delinea Secret Server token supplied during the initial authentication phase.

• Confirm whether your Delinea Secret Server utilizes a custom URL; if it does, make sure to input that custom URL into the Delinea Host field of the scan credentials.

• Ensure the Databases plugin family is enabled; this action facilitates the inclusion of all constituent plugins required for comprehensive vulnerability assessment.

• Credential values are cached for the duration of a single scan run. If credentials were rotated mid-scan, restart the scan to pick up the new values.