OAuth2 authentication for OpenVPN (and for FreeRadius)
I have two use-cases I want to enable and corresponding ideas.
A) OpenVPN server use OAuth2 as backend.
Use-case: Let my clients utilize their O365/Azure AD credentials to connect to my OpenVPN server running on pfsense.
Idea: Make it possible to authenticate using a OAuth2 backend, this should be added as a new type in the “System/User Manager/Authentication Servers”
B) FreeRadius server use OAuth2 as backend
Use-case: Let my clients utilize their O365/Azure AD credentials to connect to my local wireless network.
Idea: Network appliances (managed switches and access points) generally only speak RADIUS, so the freeradisus server in pfsense can be used if it can in turn speak OAuth2. So I suggest adding “OAuth2 Authentication” after “LDAP” in the freeradius settings. (There already exists a Perl module for freeradius which could be integrated: https://github.com/jimdigriz/freeradius-oauth2-perl)
A and B could be split up, I just thought it would be good first to have an overview of how many places OAuth2 would be relevant. If I needed to prioritize, then A has the highest value for me.
In general more and more are trying to leverage the cloud and alleviate the need for local active directory servers etc. so embedding OAuth2 across pfsense and making it easy to connect to AzureAD/O365, Google Apps etc. would really be powerful and a way to avoid duplicating user databases.
PS: I have been suggested to add my idea as a separate feature request: "OAuth2 authentication in captive portal" (https://redmine.pfsense.org/issues/3377)
Best regards Kristian Junkov
#9 Updated by Patrick Monfette over 1 year ago
+1 on my side as well. We need this in order to properly implement VPN/IPSec/FreeRadius for our remote workers to integrate the authentication with G-Suite. I was hoping for 2.4.4 but it seems it just got pushed to 2.4.5. There are third parties solutions that do it but I'd rather keep it all internal and well integrated within pfSense.