Overview

An integration is the connection to one firewall, proxy, cloud platform, or on-host enforcement point, together with the agent and credentials Knocknoc uses to reach it. You define it once, and any number of Knocs can share it.

Manage integrations under Admin > Integrations.

Why integrations

An integration holds a connection in one place, so several Knocs on the same firewall share one copy of its address and credentials instead of each carrying its own.

Rotate credentials once. Update the integration, and every Knoc that uses it follows.
No duplicated config. One connection, many Knocs.
Activity per integration. See which Knocs use it, who has been connecting, grant volumes, average wait times, and failures. Trace a problem from an access path back to the system enforcing it.

Each Knoc still defines the access it provides. The integration is the connection; the Knoc is the rule. See the Knocs page for who and the rules.

Integration types

Knocknoc integrates with several kinds of system.

Firewalls such as FortiGate, PAN-OS and SonicWall.
Cloud platforms such as AWS, Azure and GCP.
Reverse proxies such as nginx and HAProxy.
On-host enforcement running on the agent's own machine (ipset, nftables, pf, Windows Firewall, nginx, HAProxy, or a script).

Each type has its own setup page in this chapter.

Managing integrations

List. Admin > Integrations shows every integration your Knocs use. Search, filter and group to find one.
Detail. Open an integration to see which Knocs use it, its agent and last-seen status, and its access activity.
Edit. Change the connection details or rotate credentials in one place, and every Knoc that shares it follows.

Bring existing connections together

If several Knocs each hold their own copy of the same connection, Admin > Integrations > Find duplicates asks your agents to identify matching connections and lets you merge them into shared integrations, keeping every Knoc assignment. Update the listed agents first so they can compare their configurations.