Advanced Search
Search Results
459 total results found
v6.0
We're excited to announce the release of Knocknoc 6, a major leap forward in attack surface reduction, implemented at speed. This release brings a host of new features and improvements that make Knocknoc even more efficient, user-friendly, and adaptable within...
LDAP
Knocknoc can authenticate users to an LDAP server like Active Directory, by attempting to bind as that user with their password. This is useful when you have an on-premises LDAP server, and want to allow users to have a single password to manage. Knocknoc conf...
SAML
Knocknoc supports up to six identity providers for user logins, and one provider of its own for the admin portal. Separating the admin provider lets MSPs and security teams manage users and Knocs without being granted access to the services being protected. Se...
Jumpcloud
The following example assumes your Knocknoc instance is located at https://knocknoc.example.com. Wherever you see that, please substitute it for your own instance URL. Setting Up the IdP Creating An Application Log in to your JumpCloud tenant as an administrat...
Entra ID (SSO, Azure AD)
Single Sign On using Entra is simple, follow the guide below to configure Knocknoc User and/or Admin SSO, with Entra. The following example assumes your Knocknoc instance is located at https://<hosting instance>.knoc.cloud. Wherever you see that, please substi...
OKTA
The following example assumes your Knocknoc instance is located at https://knocknoc.example.com. Wherever you see that, please substitute it for your own instance URL. Setting Up the IdP Create an Application Click Create App Integration Select SAML 2.0 Set an...
Local Authentication (MFA included)
Knocknoc supports local users in addition to SAML/LDAP. Simply add a user, with a username and password. Then assign them to a group or link them within a Knoc. This is helpful for casual users, as you can set an expiry. So for example if you have a web applic...
v5.0
Current version of Knocknoc server is: 5.0.62, released on Mon, 12 Feb 2024 Current version of knocknoc-agent is: 1.0.28, released on Sat, 24 Feb 2024
IPsets with UFW
This is an example that lets you use UFW (https://wiki.ubuntu.com/UncomplicatedFirewall) and IPsets to dynamically allowlist IPs for a common host-based firewall. This is achieved in only a few steps: Install the Knocknoc orchestration agent on the UFW host ...
Licensing Knocknoc
Knocknoc licensing and pricing can be found on the Knocknoc website. Once you have obtained your license and have either completed the self-hosted install or received the login details for your cloud hosted instance: Copy your license key from the Knocknoc Lic...
Create groups
Groups in Knocknoc map users to Knocs, and a user can belong to multiple groups. To create a group: In the Knocknoc admin interface, open Identities, select the Groups tab, and click Create Group. Enter a Name. For SAML and Dynamic groups this must match the g...
Click to grant/revoke
For additional security and temporal access control, Knocs support a "click to grant" and "click to revoke" option. This requires the user to click a button after logging in, prior to each grant being processed. This offers an additional layer of security and ...
Admins
Admins in Knocknoc can log in to /admin on their Knocknoc server, however they can't be granted ACLs. This separates out regular logins from admin logins, and allows for best practice. You can create an Admin using this dialog box if required. SAML is the pref...
Settings
The Settings page is where administrators configure how Knocknoc behaves across the whole deployment: sign-in methods, the server's public address, TLS certificates, logging, threat intelligence, optional access features, and branding. It is only available to ...
Time for NTP
NTP It's important that ALL the servers within the Knocknoc cluster and agents are synchronized and set to the correct time. We recommend using chrony on a Linux VM to keep the time, but any NTP implementation would work. Time is an important aspect of authen...
LDAP troubleshooting tips
The Knocknoc server will need to be able to contact your LDAP server on port 389 or 636. This is determined by the LDAP URL in the Settings: ldap://ldap.example.com - this format says port 389 ldaps://ldap.example.com - this format is port 636 Please make sure...
Knocknoc server behind HAProxy
Running Knocknoc behind HAProxy could be a great option for people with existing HAProxy deployments, or who want to unify certificate and other management tasks. Here is a sample HAProxy config for Knocknoc as a backend: frontend knocknoc-frontend bind 0.0....
Getting Started
Cloud SaaS or self-hosted server? You can run your Knocknoc server either as a managed cloud instance (we host it) or you can self-host it. Should I deploy a cloud or self-hosted instance of Knocknoc? The answer will depend on a few factors. For example, if yo...