Director API behind proxy

  • Director version (System - About): 1.10.2
  • Icinga Web 2 version and modules (System - About): 2.11.4
  • Icinga 2 version (icinga2 --version): r2.14.0-1
  • Operating System and version: Ubuntu 22.04
  • Webserver, PHP versions:

I’m new to Icinga and just started to set things up and have set it up using a external proxy with authentication that publish the web GUI (443).
I was thinking of doing a semi-automated install of agents (for both Windows and Linux clients) and was looking into the Director (which is installed and working). I enabled Self Service API on host template and then just realized that the agent install (for instance using PS in Win) probably don’t like to first need to authenticate to the proxy to then get into the Director API? Is there anyway to safely publish the API?

Well the agent authenticates against the API with the key from the template through a TLS secured connection. A WAF on the proxy can be used to further protect the Icinga2 Master behind it.
But the agent can’t authenticate to the proxy only to the API.

OK thanks for clearing it out a bit for me. I’ll investigate how we can configure it that way.