Hello all,
we are trying to implement 2FA for several existing Firebox SSL VPNs
(which essentially uses OpenVPN on server and client side). The remote
users all use the Windows OpenVPN client. This works perfectly without
2FA, and it works also if you do not need to specify the authentication
Hi there,
On 10/03/22 11:51, Jakob Curdes wrote:
Hello all,
we are trying to implement 2FA for several existing Firebox SSL VPNs
(which essentially uses OpenVPN on server and client side). The remote
users all use the Windows OpenVPN client. This works perfectly without
2FA, and it works al
Am 10.03.2022 um 12:22 schrieb Jan Just Keijser:
Thu Mar 10 10:35:32 2022 Restart pause, 5 second(s)
*Thu Mar 10 10:35:40 2022 Previous command sent to management failed:
ERROR: Options warning: Bad backslash ('\') usage in TCP:0: remember
that backslashes are treated as shell-escapes and i
On Thu, Mar 10, 2022 at 6:14 AM Jakob Curdes wrote:
> Hello all,
>
> we are trying to implement 2FA for several existing Firebox SSL VPNs
> (which essentially uses OpenVPN on server and client side). The remote
> users all use the Windows OpenVPN client. This works perfectly without 2FA,
> and it
Hello Selva, hello all,
If you are using OpenVPN-GUI for Windows, looks like a bug. I guess,
by text window, you mean the challenge-response dialog that the GUI
pops up for 2FA.
Yes exactly.
Username is first input in the username/password dialog and that seems
to succeed with the backsl
