TOTPRadius - Cisco Meraki Client VPN
Meraki Client VPN with two-factor authentication and self-enrolment of the second factorMeraki Client VPN does not natively support two-factor authentication, a third-party solution is required for this configuration. Starting from v0.2.1 TOTPRadius can serve as an LDAP proxy, a feature that allows implementing two-factor authentication with the systems that do not natively support it.
Different from Citrix StoreFront, Meraki CVPN does not have any standard way of calling the REST API of TOTPRadius appliance. However, it is still possible to implement self-enrollment with Meraki CVPN by using VPN Connection entries prepared with Microsoft Connection Manager Administration Kit (CMAK). Detailed instructions can be found here.
Once the TOTPRadius appliance has been installed and initialized, configure the following settings on the General settings page:
► Set or generate a new Radius secret
► In the Endpoint IP and subnet fields specify the parameters of your Meraki MX device
► Set LDAP as enabled
► Specify the LDAP server IP/FQDN and the format of the username (%firstname.lastname@example.org or DOMAIN\%username% format, where "DOMAIN" or "domain.local" need to be replaced with the domain name or removed if needed )
► If you decide to allow self-enrollment, make sure "Allow ldap enrollment" parameter is enabled. In the same section you can also allow re-enrollment and modify the intro text of the LDAP web enrollment page.
Once the TOTPRadius appliance has been configured , the following steps outline how to configure Client VPN to use TOTPRadius:
► Log onto the Cisco Meraki Dashboard and navigate to Configure > Client VPN.
► Select the option to enable the Client VPN Sever.
► Set the Client VPN Subnet. This will be a unique IP subnet offered to clients connecting to the MX Security Appliance via a Client VPN connection.
► Specify the DNS servers.
► Enter a shared secret that will be used by the client devices to establish the VPN connection. Note: This is a different value from the RADIUS shared secret.
► Select RADIUS as the Authentication method.
► Click the Add a RADIUS Server link.
► Enter your TOTPRadius IP Address.
► Enter the RADIUS Port that the MX Security Appliance will use to communicate to the NPS server. For TOTPRadius integration keep the port as 1812.
► Enter the RADIUS Shared Secret (established when the MX was added as an authenticator).
► Click Save changes.
Installation of additional software is not required on client devices. The Cisco Meraki Client VPN solution uses L2TP over IPsec, which is supported by almost all device's built-in native clients. Refer to Meraki Client VPN documentation for client configuration instructions.However, the standard methods of creating Client VPN connection entries for Meraki are not supporting self-enrollment feature. To create VPN Connection entries, refer to our CMAK guide.
- Installation and initial configuration
- Network configuration
- Migrating from older versions
- LDAP Configuration
- Azure AD Configuration
- Self-service enrollment portal
- Web and LDAPS Certificates
- Syslog configuration
- Single-factor authentication exceptions
- Slave appliance mode
- Dynamic RADIUS Attributes
Manage and use TOTP/HOTP codes via Python CLI script using a PC/SC device (USB NFC) or directly via USB. A cross-platform solution that works under Windows, macOS and Linux platforms.
Python-based tools are essential not only for their cross-platform compatibility, but also because their source-available nature allows experts/developers to examine the source code, ensuring transparency and minimizing the risk of hidden vulnerabilities or malicious elements. A GUI wrapper for the script is also available.
Token2 is excited to announce the upcoming mass production of their revolutionary PIN+ series, a line of FIDO2 Security keys. These security keys feature advanced PIN complexity rules that set a new standard for security. The firmware development for the PIN+ series is now complete, and the company is currently making preparations for mass production.
In a significant development for iOS users, Microsoft Azure Active Directory (AD) has expanded its support for FIDO2 security keys on the Safari browser. This advancement is a crucial step towards enhancing security and usability on Apple's mobile devices, ensuring seamless authentication experiences for Azure AD users. With FIDO2 security keys, users can now enjoy passwordless access to their Azure AD accounts, boosting convenience and significantly reducing the risk of password-related attacks. Let's dive deeper into this exciting development and explore the benefits it brings to iOS users.