
amvov (amvov) asked a question.
The Okta RADIUS agent doesn't currently support MSCHAPv2 (see https://help.okta.com/en/prod/Content/Topics/DeploymentGuides/Radius_Server_Agent/radius-server-agent-dg.htm)
Doe to this limitation, I cannot use Okta RADIUS to authenticate IKEv2 VPN users on my Watchguard VPN server. Is MS-CHAPv2 on the roadmap for the Okta RADIUS client?

Did you ever get a response, ticket closure, or solution for this? I am running into the same thing.
I have a Watchguard, and it's using LDAP right now for login. But it's not MFA. Obviously this is a big security risk.
I wanted to use RADIUS via Okta, but alas came up with this post.
So what's the story here? I bought the so-called Universal Directory, but everywhere that seems to require a directory, it's not universal-enough without a hybrid architecture (RADIUS, AD LDS queries, AD queries, and so on can't be done without local servers). It's basically just a public facing LDAP server as far as I can tell...
Hi Michael,
No, I never received any reply or update, however I did get RADIUS auth to work for my Watchguard VPN. The problem is that Mobile VPN with IKEv2 requires MS-CHAPv2. Without it, I had to settle for IPSec, which is vulnerable to CVE-2002-1623 (https://nvd.nist.gov/vuln/detail/CVE-2002-1623).
Note that you can also set up the Watchguard Access Portal, which supports SAML authentication and doesn't require RADIUS at all, though it is not very scalable.
Yea, my users generally need actual network access, not just webpage stuff so the web portal doesn't work for us.
I also am in the process of downgrading to to use VPN with SSL and finding a place to stick the Okta RADIUS Server application....I've been whittling away at local servers, but the need for something like that keeps popping up...
I have one addendum to this....configured as LDAP on the Watchguard, and it *did* send me Okta Verify pushes as part of the verification chain with Mobile VPN with SSL. So, good 2FA there without the need for the RADIUS agent on a server.