[SOLVED] Setting up RoadWarrior OpenVPN

[purpleimpala]

I'm using OPNsense 6.1.16-amd64, and following the instructions at https://docs.opnsense.org/manual/how-tos/sslvpn_client.html .  I am trying to set up 2FA.

(Aside: there's some material missing in Step 0: Preparation in the section entitled "Create a Certificate" where it says "Fill in the form with (leave the rest default):".  Here it needs to mention that the certificate to be created is a Server certificate called "SSLVPN Server Certificate" (for example, to match the text later).)

My problem comes in Step 1: Add SSL server.  When you click the orange box saying "+ Add Server", the form doesn't include a field to select the Backend Authenticator.  This means that when you click "Save", you get an error message at the top of the form pointing out that you must select a Backend Authentication method, but you can't.

If you use the Wizard to add a server (which took me a bit of working out - it's not so obvious that you can click on the magic wand) then at least you can add a server, because the first step is to set up a new Authentication Backend of one of three types (but none of them are OTP unfortunately).

Is there a workaround for this?

[franco]

Make sure your firmware version is 16.1.16, and that you do execute Step 0 "Configure TOTP server". If there is no TOTP server, you will not be able to select it in Step 1.

[greY]

I have the same issue with 16.1.16, there is no "Backend for authentication" option field (totp Server is configured)

[purpleimpala]

Yes, it is 16.1.16, and yes, the TOTP server is configured and present.  The point is, the OpenVPN "Add Server" dialog doesn't have a field for selecting the backend.

BTW this is a fresh install of OPNsense.

OPNsense 16.1.16-amd64
FreeBSD 10.2-RELEASE-p18
OpenSSL 1.0.2h 3 May 2016

[franco]

Ah, I can see now. Can you try this fix run from the root console shell (Option 8):

# opnsense-patch 6ffc213

[greY]

woked for me, thx!

[franco]

Ok, thanks for confirming. This will be shipping in 16.1.17. A mobile portability fix interfered with the addition of this field.

[purpleimpala]

Yes, I can see and select the field as expected with this patch. Thanks!

[franco]

Ok, sorry about the hiccup here. 16.1.17 will be released on Wednesday.