ReadTheNetwork Posted December 21, 2017 Posted December 21, 2017 Hi all, Looking ahead to see if we can save costs, I'm looking at changing our system slightly to PFSense and Squid. I've heard good reviews on this so thought I'd give it a go. Currently I'm getting Firefox and Chrome asking for authentication (IE seems to work fine). Is there a way around this? Thanks 1
MatthewL Posted December 21, 2017 Posted December 21, 2017 On Chrome are HTTPS sites ok but prompting for authentication on HTTP?
ReadTheNetwork Posted December 21, 2017 Author Posted December 21, 2017 Both HTTP and HTTPS are prompting for authentication (on FF and Chrome). Seems to work fine after entering the credentials.
Geoff Posted December 21, 2017 Posted December 21, 2017 Lazy way to fix this: https://pf2ad.mundounix.com.br/en/index.html
FN-GM Posted December 21, 2017 Posted December 21, 2017 Just as a side note. Make sure the CPU supports AES-NI or else you won't be able to use PFsense 2.5
ReadTheNetwork Posted December 22, 2017 Author Posted December 22, 2017 I've been using the RADIUS method which has been working (with FF and Chrome prompting for authentication), but when I try to use the LDAP it keeps failing to connect for users. The settings I have for LDAP are: Authentication Server: 192.168.0.1 (IP address of the AD server) Port: 389 LDAP Version: 3 LDAP Server User DN: cn=pfsenseuser,ou=account users,dc=mydomain,dc=sch,dc=uk LDAP password: Password LDAP Base Domain: dc=mydomain,dc=sch,dc=uk ldap username DC Attribute: uid ldap search filter: (samaccountname=%s)
Geoff Posted December 22, 2017 Posted December 22, 2017 Windows AD DCs require you to connect via LDAPS rather than LDAP. Configure your SSL.
ReadTheNetwork Posted December 22, 2017 Author Posted December 22, 2017 Testing with ldp.exe I seem to be able to connect using 389 :/
ReadTheNetwork Posted December 22, 2017 Author Posted December 22, 2017 Not yet, that'll be another holiday upgrade to do.
diladele Posted December 22, 2017 Posted December 22, 2017 But I was talking not about LDAP authentication but Kerberos. The idea is to setup a designated user in the AD, map a special proxy name to it and enable negotiate authentication on Squid. After that it all automatically and transparently handled by users's browser (or course the machine need to be AD joined). Might be a challenge to setup but after that it just works for years.
ADMaster Posted December 23, 2017 Posted December 23, 2017 I've been using the RADIUS method which has been working (with FF and Chrome prompting for authentication), but when I try to use the LDAP it keeps failing to connect for users. The settings I have for LDAP are: Authentication Server: 192.168.0.1 (IP address of the AD server) Port: 389 LDAP Version: 3 LDAP Server User DN: cn=pfsenseuser,ou=account users,dc=mydomain,dc=sch,dc=uk LDAP password: Password LDAP Base Domain: dc=mydomain,dc=sch,dc=uk ldap username DC Attribute: uid ldap search filter: (samaccountname=%s) I don't use pfsense or squid, but the samaccountname is the username in AD. Try changing this line. ldap username DC Attribute: samaccountname It would also be good to move to ldaps but should function without it.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now