Self-enrollment
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.
TOTPRadius configuration
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 (%username%@domain.local 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.
Dashboard Configuration
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.
Client Configuration
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.
