Navigation

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

    Allow User To Authenticate and Bypass Filter

    Cache/Proxy
    3
    5
    1219
    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.
    • W
      Willo last edited by

      Hi Guys,

      I'm very new to PFSense and I'm having some issues navigating some finer grained details.  I have a SquidGuard web filter rule enabled and all working well.  It's mainly for the younger guests of the house and I'd like to be able to authenticate and bypass or continue through the filter.

      I've seen settings to exclude IP's, but I need it for users.

      Any clues?

      Cheers

      Willo

      1 Reply Last reply Reply Quote 0
      • C
        chris4916 last edited by

        Well… this is pretty straightforward... but requires that you authenticate users.
        Which means not transparent proxy.
        Then you can easily have rules for either users of better, group of users allowed to access what could be denied to other groups (i.e. kids)

        1 Reply Last reply Reply Quote 0
        • R
          rjcrowder last edited by

          I did something similar to what you are describing for Dansguardian. See this thread https://forum.pfsense.org/index.php?topic=68872.msg376980#msg376980

          It's a lot of custom work - but you could do the same approach for squidguard…

          1 Reply Last reply Reply Quote 0
          • W
            Willo last edited by

            @chris4916:

            Well… this is pretty straightforward... but requires that you authenticate users.
            Which means not transparent proxy.
            Then you can easily have rules for either users of better, group of users allowed to access what could be denied to other groups (i.e. kids)

            @rjcrowder:

            I did something similar to what you are describing for Dansguardian. See this thread https://forum.pfsense.org/index.php?topic=68872.msg376980#msg376980

            It's a lot of custom work - but you could do the same approach for squidguard…

            Thanks heaps for the replies.  @rjcrowder, too much custom work isn't an option unfortunately, if things break it's admin overhead I don't have the time for :(

            @chris4916, I'm wondering if the authentication couldn't be "transparent" by authenticating to either a local user database or AD?  So when they browse, it silently authenticates in the background?

            I've come off a Fortigate appliance to PFSense and in their case, if the page was filtered there was an override feature allowing you to enter your username and password and if you were allowed you could proceed based on credentials.

            Thoughts..

            1 Reply Last reply Reply Quote 0
            • C
              chris4916 last edited by

              @Willo:

              @chris4916, I'm wondering if the authentication couldn't be "transparent" by authenticating to either a local user database or AD?  So when they browse, it silently authenticates in the background?

              This wording is quite confusing especially when topic is proxy. Avoid "transparent authentication" wording, IMHO  ;)

              This said, technically, yes you can enable SSO (single sign on) at browser level and configure Squid (and your browser) to support Kerberos (because SSO is Kerberos based) but be aware that:

              1 - this is an extra level of complexity. Perhaps not the one to start with
              2 - Behaviour differs depending on browsers
              3 - This works with Squid / Squidguard but I don't know if pfSense packages allows such configuration
              4 - last but not least, this means to have Kerberos domain configured (and used). This is often achieved with Windows domain.

              I would suggest that you not try to achieve everything from scratch in one shot.

              Start with authentication and filter then once this works, you can think about changing your authentication mechanism and move to SSO

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              Products

              • Platform Overview
              • TNSR
              • pfSense
              • Appliances

              Services

              • Training
              • Professional Services

              Support

              • Subscription Plans
              • Contact Support
              • Product Lifecycle
              • Documentation

              News

              • Media Coverage
              • Press
              • Events

              Resources

              • Blog
              • FAQ
              • Find a Partner
              • Resource Library
              • Security Information

              Company

              • About Us
              • Careers
              • Partners
              • Contact Us
              • Legal
              Our Mission

              We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

              Subscribe to our Newsletter

              Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

              © 2021 Rubicon Communications, LLC | Privacy Policy