Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    OpenVPN Multi-Factor

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 1.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Seppic
      last edited by

      So, I have pfSense/OpenVPN installed and LDAP authentication to only allow a group of users to access the VPN with their AD credentials.  Everything is working great for my first step.  My next step though I'm having a little trouble tackling and that's multi-factor.  I know we're shooting for something along the lines of Google Authenticator or a similar application time based token that changes every so often.  Something either extremely cheap/free would be preferred for the little amount of VPN use we actually have.

      Essentially I want the user to have to type in their domain credentials and then also have to type in this rotating one time password.  Are there any guides out there on how to accomplish this and tie it into this currently working system?

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        Other than making it a pain in the ass for the user what is the actual point of this?

        So the user has to have the cert, or atleast that is how you should have vpn setup.  So they need their cert and the creds to auth with, so their you go mfa already.  Something they have (the cert) and something they know, their AD creds.

        Why the time based token?  Other than making it a PITA for the users to actually use the vpn? ;)

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        1 Reply Last reply Reply Quote 0
        • S
          Seppic
          last edited by

          Currently they only VPN in with their AD credentials.  I want them to have to enter their AD credentials and a token code.  Requiring a token code from a separate device is much more secure than a certificate alone especially if a user has their workstation/password compromised.  It also takes away from having to manage individual user/machine certificates.  The last 3 places I've worked required RSA hardware tokens, but the team here wants to try out an application based token such as Google Auth/Duo/Authy.  I'm well aware the ease of using a certificate/credential alone, but that's not the direction we chose to go.  Thank you for your input though :)

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.