Skip to content

Troubleshooting

If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

Debug Logs

For information about managing additional source settings, including debug logging and downloading connector logs, refer to Managing Additional Settings.

Test Connection fails with an authentication error (HTTP 401 or 403)

The following error might appear when you select Test Connection:

Authentication failed. Please check the credentials in Connection Settings.

SailPoint returns a generic authentication message by design and includes a request ID for support correlation.

Resolution: Confirm that the Access ID and the Access Key or UID Token in Connection Settings match the authentication method in Akeyless. Confirm that the authentication method is still enabled and that the Access Key or UID Token was not rotated without updating SailPoint.

SailPoint cannot reach the Akeyless API

Test Connection fails because SailPoint cannot reach the Akeyless API host.

Resolution: Confirm that Akeyless API URL uses the correct host and the HTTPS scheme. For public SaaS, use https://api.akeyless.io. For a dedicated or self-hosted deployment, use your tenant API URL. Confirm that network and firewall rules allow traffic from SailPoint to that URL. The URL must use HTTPS.

Test Connection fails with a not found (HTTP 404) response

The Akeyless API returns HTTP 404 when the request URL does not match your deployment.

Resolution: Verify that Akeyless API URL is correct for public SaaS. For more information, refer to Supported Managed Systems.

Test Connection or aggregation is rate limited (HTTP 429)

Akeyless returns HTTP 429 when SailPoint sends too many requests in a short period.

Resolution: Wait, then select Test Connection again. The connector retries automatically. If the error continues, reduce concurrent test or aggregation activity against the same Akeyless tenant.

Test Connection fails because of a TLS or certificate problem

The connection fails during TLS handshake or certificate validation for the Akeyless API URL.

Resolution: Confirm that the certificate for the Akeyless API host is valid and matches the hostname in Akeyless API URL. Check for TLS inspection, expired certificates, or a hostname mismatch.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.