Error integrating Threat Analytics with Symantec PAM
search cancel

Error integrating Threat Analytics with Symantec PAM

book

Article ID: 395630

calendar_today

Updated On:

Products

CA Threat Analytics for PAM

Issue/Introduction

When attempting to enable Threat Analytics integration with Symantec Privileged Access Manager (PAM), the following error message is displayed in the Threat Analytics interface, under the Configuration tab:

    "Error! Threat Analytics was unable to connect to CAPAM with the provider Adapter Configuration. Please, check the log details."

Observed Behavior:

  •     Error occurs after entering the relevant "Host", "Username", and "Password" fields for the PAM user in Threat Analytics.
  •     Threat Analytics logs do not show any specific errors.
  •     On the PAM side, under Licensing, the license for Threat Analytics is displayed as Enabled.

 

Cause

This error usually points to a configuration or secure connection issue between Threat Analytics and Symantec PAM—often related to SSL validation, incorrect connection details, or insufficient permissions.

Resolution

To resolve this issue, follow these steps:

   1.  Configure Threat Analytics Connection on PAM:

        -  In the Symantec PAM interface, navigate to:

        Configuration → Symantec Modules → Threat Analytics

        - Fill out the following fields:

            - Threat Analytics Server Address

            - Authentication Token

            - Service Identifier

       - If you are not using SSL for this integration, uncheck the "SSL Validation" checkbox.

    2. Test the Connection:

        -  After disabling "SSL Validation" (if applicable), attempt the integration again.

        - The connection should now be successful from PAM to Threat Analytics.

Additional Information

If the issue persists after following the steps above:

    - Ensure all provided server addresses, tokens, and IDs are correct.

    - Verify network connectivity and that no firewalls or proxies are blocking the connection.

    - Double-check that both PAM and Threat Analytics are operating compatible versions.