Breadcrumbs

Fixing Webhook and Syslog Target Trust Issues in ASGARD Analysis Cockpit

Last update:
Last verified version: AAC 4.4.3

Overview

You receive this error when sending Notifications to Webhook or Syslog targets because the Analysis Cockpit does not trust the target:

"Could not post to webhook "MY_WEBHOOK" at "https://xyz.com/api/v1/case ":
Post "https://xyz/api/v1/case": tls: failed to verify certificate: x509: certificate signed by unknown authority

This article explains how to avoid TLS issues in Webhook communication with the Analysis Cockpit.

Prerequisites

  • Console root access to ASGARD

  • Existing CA infrastructure

Expected Result

The Analysis Cockpit trusts the target. It transmits notifications and logs reliable and securely. No more error messages will be generated in this regard.

Steps to proceed

  1. Load the CA that signed the target system's TLS certificate into your Cockpit.

  2. Move the certificate to the local CA folder:

    Bash
    sudo -s
mv my_ca.crt /usr/local/share/ca-certificates

  3. Import the certificate into Debian's Trust Store:

    Bash
    update-ca-certificates

Related Content