Bobcares

pfSense HAProxy Authentication | Tutorial Note

by | Jul 4, 2023

Read this article to know a simple method to enable pfSense HAProxy Authentication. Bobcares, as a part of our pfSense Support offers solutions to every query that comes our way.

Steps for pfSense HAProxy Authentication

Step 1: Make Custom Password Encryption

Make a unique password using an example hash. Here, we use Debian.

  • Now install the whois package using the code below:
    sudo apt install whois
  • Then use the below code to create the password hash after the installation.
    printf "TheSuperSecretPasswordHere" | mkpasswd --stdin --method=sha-512
  • Now we can see the below text:
    apauna@MSI:~$ printf “TheSuperSecretPasswordHere” | mkpasswd –stdin –method=sha-512
    $6$uQz8XOERPi$ylyDGyzAhXIT3k.PwqhJoIULW21UvhjyHX2zoR.wsLBDLnBvEo3TlYNrClXNh/58w5j/F4DZxfXGPbykTHTDR/
  • Use the final line and save it in Custom Options.

Pfsense haproxy authentication

Step 2: Change the Settings Custom Options
  • In pfSense, add Custom Option on the Settings page.
  • It is important to set up special user groups like the one below in order to use Authentication.
    userlist UserGroup
    user admin password <Password hash from step 1 above>
    
  • Remember to make these two lines the last items in the custom options list.
  • After saving, edit the backend to use the custom authentications. We can add as many users as needed for access. Here, we’re considering only one user.
Step 3: Add ACl to the backend in HAProxy
  • Open Backend in the issue.
  • Click the pointer to the far right of the item we want to change.
  • Then on the backend editor, dropdown the Access control lists and Actions item.
  • Take note of the name, Custom acl: dropdown item, and associated http_auth(UserGroup) Note: The usergroup indicated above was created in step 2 above, therefore use the same name as in step 2. It’s named “UserGroup” in here.
  • Example of an ACL Action that associates acl with the “UserGroup” realm unless BackendAccess authentication is used. Again, this should correspond to the user group name specified in Step 2 above.

[Looking for a solution to another query? We are just a click away.]

Conclusion

With a HAProxy package for pfSense, we’ll be having a good web UI, along with a reliable and flexible open-source load balancer for TCP and HTTP. To conclude, we provide a simple method from our Support team to enable pfSense HAProxy authentication.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF