Authentication
A guide on configuring the various authentication methods for Knocknoc
Local Authentication (MFA included)
Knocknoc supports local users in addition to SAML/LDAP. Simply add a user, with a username and pa...
SAML
Knocknoc supports up to six identity providers for user logins, and one provider of its own for t...
Entra ID (SSO, Azure AD)
Single Sign On using Entra is simple, follow the guide below to configure Knocknoc User and/or Ad...
OKTA
The following example assumes your Knocknoc instance is located at https://demo.knoc.cloud. Where...
G Suite (Google)
G Suite can be set up as an Identity Provider if you have G Suite Business Starter or above plan....
CyberArk
CyberArk integrates with Knocknoc via the "Web Apps" component, passing through SAML assertions. ...
Authentik
In this example our authentik instance is hosted at https://auth.example.com/ and is running vers...
1Kosmos
Configure 1Kosmos as a SAML identity provider (IdP) for Knocknoc. Once connected, your users auth...
Ping Identity
Ping Identity SSO Configure PingOne as a SAML identity provider (IdP) for Knocknoc. Users authent...
Keycloak
Keycloak supports multiple authentication realms, so you must first select the appropriate realm ...
Jumpcloud
The following example assumes your Knocknoc instance is located at https://demo.knoc.cloud. Where...
ADFS
The following example assumes your Knocknoc instance is located at https://your-knocknoc.cloud/. ...
LDAP
Knocknoc can authenticate users to an LDAP server like Active Directory, by attempting to bind as...
LDAP troubleshooting tips
The Knocknoc server will need to be able to contact your LDAP server on port 389 or 636. This is ...