JumpCloud RADIUS gives you the power and security of RADIUS network authentication without the need for physical servers. Learn how to configure OpenVPN Access Server to use JumpCloud RADIUS for authentication.<\/p>\n\n\n\n
Prerequisites<\/strong>:<\/p>\n\n\n\n
Considerations<\/strong>: <\/p>\n\n\n\n
To configure OpenVPN Access Server to use JumpCloud RADIUS:<\/p>\n\n\n\n
<\/p><\/div>
Use multiple JumpCloud RADIUS IPs for redundancy.<\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
<\/p><\/div>
MS-CHAP v2 is the recommended authentication method. <\/p>\n <\/div><\/div><\/div><\/div>\n\n\n\n
The OpenVPN Access Server provides the command line utility “authcli” to validate your JumpCloud authentication and authorization configuration. <\/p>\n\n\n\n
PATH:<\/strong> \/usr\/local\/openvpn_as\/scripts\/authcli\u00a0<\/kbd><\/p>\n\n\n\n
USAGE<\/strong>: authcli –user JumpCloud_Username<\/kbd>
<\/p>\n\n\n\n
For additional diagnostic information, you can enable Debug Level logging in the OpenVPN Access Server ‘as.conf’ configuration file, restart the service and review the log messages within the default “\/var\/log\/openvpnas.log” file.<\/p>\n\n\n\n
$ sudo echo “DEBUG_AUTH=true” >> \/user\/local\/openvpn_as\/etc\/as.conf
$ sudo service openvpnas restart <\/p>\n<\/div><\/div>\n\n\n\n
When troubleshooting is complete, edit the configuration file to comment out the DEBUG reference, and restart the service to return to normal operation.<\/p>\n\n\n\n
#DEBUG_AUTH=true
$ sudo service openvpnas restart <\/p>\n<\/div><\/div>\n\n\n\n
For additional information on troubleshooting authentication and enabling debug level logging, see OpenVPN Troubleshooting Authentication Related Problems (authcli)<\/a> to learn more.<\/p>\n","protected":false},"excerpt":{"rendered":"