Search Results

The Knocknoc OpenBSD Agent is orchestration software for managing just-in-time network access. It runs as the unprivileged _knocknoc-agent user, connects to your Knocknoc server over WebSocket, and enforces access locally through the configured integrations. ...

Knocknoc integrates with the PF packet filter to dynamically control network access on a host that the agent runs on directly. As users authenticate and grants expire, the agent adds and removes their IPs from a PF table; your own pass/block rules reference th...

Knocknoc normally grants access to the single IP a user authenticates from. Agentic Access and Companions extend that for two cases: granting time-limited access to an automated agent, and keeping access for a user's other companions, such as a second device o...

Knocknoc can orchestrate F5 Networks BigIP and related devices via two mechanisms, including iRules "Data group List" and the AFM. Typically iRules are used as they can be deployed across both high-end F5 devices and lower/smaller deployments. The iRules can r...

The Overview tab under Identities is the first thing you see when you open Identities in the admin interface. It gives you one place to see what your users, groups and admins have been doing recently, without opening each identity one at a time. Activity chart...

Agent error code #F5000 indicates that the Knocknoc agent could not establish a network connection to the F5 BIG-IP management endpoint at all. The connection failed before any authentication could take place. This is distinct from authentication (#F5001) and ...

Agent error code #F5001 indicates that the F5 BIG-IP rejected the username and password supplied by the Knocknoc agent. The device returned HTTP 401 Unauthorized when the agent tried to obtain an authentication token. This is distinct from authorization failur...

Agent error code #F5002 indicates that the F5 BIG-IP accepted the credentials but the user's role does not have permission to perform the requested operation on the data-group. The device returned HTTP 403 Forbidden. This is distinct from authentication failur...

Agent error code #F5003 indicates that the TLS handshake with the F5 BIG-IP management endpoint failed. The agent reached the device but could not verify its certificate. Common causes include: The BIG-IP presents its default self-signed management certificate...

Agent error code #F5004 indicates that a request to the F5 BIG-IP management endpoint did not complete within the allowed time. The device did not respond, or responded too slowly. Common causes include: The BIG-IP management plane is under heavy load or unres...

Agent error code #F5005 indicates that the login request to /mgmt/shared/authn/login did not return a usable token, even though the agent reached the device. The response was missing the token, or the login endpoint returned an unexpected result that was not ...

Agent error code #F5050 indicates that the agent authenticated successfully but the GET request for the configured internal data-group failed for a reason other than the data-group simply not existing (which is reported as #F5051). Common causes include: A tra...

Agent error code #F5051 indicates that the internal data-group named in the Knocknoc backend does not exist in the configured partition on the F5 BIG-IP. The device returned HTTP 404 Not Found. Knocknoc does not create the data-group; an administrator must cre...

Agent error code #F5052 indicates that the configured data-group exists, but it is not an Address (type ip) data-group. Knocknoc stores granted IPs as address records, so the target must be an address data-group. Common causes include: The data-group was crea...

Agent error code #F5053 indicates that the PATCH request to update the data-group's records failed. The agent could read the data-group but could not write the new record set. Common causes include: The service account's role can read but not modify the data-g...

Agent error code #F5400 indicates that the F5 BIG-IP returned a response the agent could not interpret: a body that did not parse as the expected iControl REST JSON, or an unexpected HTTP status that did not map to a more specific code. Common causes include: ...

Knocknoc 26.07.1 is one of our biggest releases to date. It reworks how you see and manage the people, devices and sessions accessing your network, improves multi-server high availability enablement that you can configure from the admin portal, ships two new i...

Agent error code #CFL100 indicates that the Knocknoc Cloudflare Lists backend has neither a List ID nor a List Name configured. The agent cannot tell which Cloudflare rule list to update, so the grant fails before any Cloudflare connection is made. Steps to Re...