how connect freeradius to MS AD

[soheil.amiri]

thanks for your reply @free4
you are right, it's better i use pfsense LDAP option to route authentication directly to MS active directory server but how can i control users Quota ?
captive portal have Quota option that help me to limiting users internet usage i know after exceed internet quota user will disconnected from CP, if the user try to connecting again, user will have internet access !!! did you test this scenario @free4
to preventing users to loging again, after exceeding their internet quota i want to use freeradius.

[soheil.amiri]

i try your command
here is pfsense\system\general log file

[soheil.amiri]

@free4 hi
I am waiting for your solution ?

[free4]

@soheil-amiri Hi,

I have been able to reproduce your issue and i guess i found a solution. Your problem can be divided in 3 part :

1. First, you are currently using mschapv1/mschapv2. CHAP protocol is incompatible with the Microsoft implementation of the LDAP protocol, so you will need to use PAP instead. Unlike OpenLDAP, Microsoft AD will never disclose the password associated to an user.
   (For the details : Freeradius can work with LDAP in two ways : "You provide me a hashed password that i will compare with the password that the LDAP server will give me" or "You provide me a cleartext password that i will submit to the AD server to check if it is valid". Only the second one is supported by Microsoft).

2. Appart from this CHAP issue....The main problem is strongly related to the fact that Freeradius shouldn't be on a router : When running the LDAP module, freeradius expect to be running on a computer which is part of the AD domain. This is not the case of your pfSense router, and this is what causes the timeout you are seeing in your logs.

more precisely, FreeRadius expect that the computer it is running on to use the Domain Controller as DNS server. FreeRadius internally perform multiple DNS request to DomainDnsZone.mylab.com and ForestDnsZones.mylab.com when using the LDAP module (for more info, please check the purpose of chase_referrals)

In order to use FreeRadius for your needs, you need to setup pfSense to use the DNS of your Active Directory Domain Controller. This can be done in System->General Settings page

This will of course have strong implications, and may not be compatible with other pfSense services that you are running. It all depends how is set up your AD domain, and especially its DNS part.

3. Finally, it seems that there is a bug in FreeRadius 3.X, it seems to fail to correctly detect the LDAP module and returns "Authentication failed because no authentication method is available".

In order to overcome this problem, you can edit /usr/local/etc/raddb/sites-enabled/default manually, and add this After the redundant {} section :

        update control { 
                Auth-Type := LDAP 
        } 

Like this :

You will need to edit this file after each update of the FreeRadius config. After each edit, you will need to execute the command "service radiusd stop && radiusd" to restart freeradius.

---

Apart from this 3 issues, the FreeRadius Package is working correctly with LDAP for me.
I Will post here my configuration for the record :

[soheil.amiri]

dear @free4
thanks for your answer
i tried your solution
here is my configuration
NAS server (work fine)

Pfsense DNS configuration (work fine)

RADIUS config

my virtual-server configuration

but my authentication test is failed
system log

[dragoangel]

@free4 your explenation is great, thanks! You saved part of my time. I want to add litle trick to your comment:
my pfSense is use Unbound transparent resolver over TLS to Cloudflare, and Windows DNS can't do TLS stuff so their upstream is pfSense, and DNS resolvers for end-clients is AD controllers. I don't want remove this flow, so I simply add to my Unbound config:

# Local resolving for AD domains
local-zone: "subdomain1.active-directory.com" transparent
private-domain: "subdomain1.active-directory.com"
local-zone: "subdomain2.active-directory.com" transparent
private-domain: "subdomain2.active-directory.com"

# Forwarding
forward-zone:
        name: "subdomain1.active-directory.com."
        forward-addr: 10.1.0.10
        forward-addr: 10.1.0.20
        forward-addr: 2001:xxxx:xxxx:1::10
        forward-addr: 2001:xxxx:xxxx:1::20
        forward-first: yes
        forward-no-cache: yes
forward-zone:
        name: "subdomain2.active-directory.com."
        forward-addr: 10.1.0.30
        forward-addr: 10.1.0.40
        forward-addr: 2001:xxxx:xxxx:1::30
        forward-addr: 2001:xxxx:xxxx:1::40
        forward-first: yes
        forward-no-cache: yes

After this pfSense can lookup to any AD record.

[dragoangel]

@free4 but still I can't authorize via FreeRADIUS.

1. Plaintext LDAP over 389 is not secure and MUSN'T be used, but atleast it suceffully connect to dc1.subdomain1.active-directory.com. Still strange logs appiers:

Mar 29 12:53:29	radiusd	13316	(0) Login incorrect (Failed retrieving values required to evaluate condition): [someuser] (from client pfsense port 0) someuser
Mar 29 12:53:29	radiusd	13316	rlm_ldap (ldap): Opening additional connection (1), 1 of 1 pending slots used
Mar 29 12:53:29	radiusd	13316	Need 1 more connections to reach min connections (1)
Mar 29 12:53:29	radiusd	13316	rlm_ldap (ldap): Deleting connection (0) - Was referred to a different LDAP server
Mar 29 12:53:29	radiusd	13316	rlm_ldap (ldap): Opening additional connection (0), 1 of 1 pending slots used

Deleting connection (0) - Was referred to a different LDAP server is really strange one.
Another case is: filter issues? What is correct filter ro MS AD? I saw many examples but still all diferent. My current config:
Filter: (sAMAccountName=%{%{Stripped-User-Name}:-%{User-Name}})
Base Filter: (objectClass=*)

2. For my configuration LDAPS dosn't works.
   Root and Intermidiate CA with DC Certs in pfSense Cert Manager. I genereted CSR on DCs and signed them by Intermidiate CA on pfSensne after witch imported them to DCs. Create GPO to put Root CA to Trusted, and Intermidiate CA to Intermidiate CAs store. All DCs trust each-other fine.
   But in SystemLogs:

rlm_ldap (ldap): Bind with CN=some-user,CN=Users,DC=subdomain1,DC=active-directory,DC=com to ldap://dc1.subdomain1.active-directory.com:636 failed: Can't contact LDAP server

Where to look why it doesn't work?
I already checked:

• telnet to dc1.subdomain1.active-directory.com:636 from pfSense works;
• dc1.subdomain1.active-directory.com is work with correct SSL certificate. Tested from my PC via LDAP utility.

Tried FreeRADIUS LDAP config many combinations:

• SSL CA Certificate: none (auto) or choose Root CA or choose Intermidiate CA
• SSL Server Certificate: none (auto) or choose DC1 Server CA
• Choose Certificate Verification Method: tried all of them.

I gived up, and begin use Windows Radius over pfSense FreeRADIUS

P.S.
@soheil-amiri have same issue in SystemLog: Deleting connection (0) - Was referred to a different LDAP server
The only info on Inet about this is https://github.com/FreeRADIUS/freeradius-server/issues/1969
But I can't understand how them can be referred to a different LDAP server, and how do I figure out what this server is?

[luisenrique]

great explanation.. when i start to setup captive portal/radius i not found any solution like described here... them i configured my enviroment adding a radius server role on domain controller to setup.. and today is working well .. for example making filted setting calback option adding MAC Adress autorize to connect to the user setting on AD..
but is good to know maybe in near future i wiil make my setup like described here
thanks

[free4]

@luisenrique pfsense support Microsoft AD authentication for captive portal for out of the box, why would you need a radius server?

[dragoangel]

@free4 for my radius needed to authorize of WPA ESK. And pfSense authorization for MS AD is poor on second dc controller. Only one option for second controller create additional "connection". Most people who care about safety have 2 DC in domain, or maybe even more. When freeRadius have load-balacer with failover, except it not working

[soheil.amiri]

hi @free4
do you have any idea about this error ?

Login incorrect ( failed retrieving values required to evaluate condition )

it would so nice to solve this issue.

[jt]

EDIT: turns out i missed an important part of the logs - the is actually freeradius thinks my user's password is incorrect ("if (ok && User-Password) -> FALSE"), so the "Auth-Type := LDAP" is actually ignored correctly. but now the question is, what's different in the live setup via CISCO WLC 2504, in comparison to running radtest, which authenticates just fine :/

*has this been resolved?
I put together bits and pieces from various forums, and kinda got this working, but, the only way to get an LDAP user authenticated, is to run
"radtest <user> <pass> 127.0.0.1 1812 <secret>"
which returns Access-Accept

if I try to login to a real WLAN (cisco WLC 2504) hooked up to the same freeradius, the user gets Authenticated, but not Authorized - according to logs
"ERROR: No Auth-Type found: rejecting the user via Post-Auth-Type = Reject
(3) Failed to authenticate the user"

a "Auth-Type := LDAP" is configured in case of successfull authentication, which is correctly respected when testing locally with radtest (see above), however, the live test receives "Access-Rejected" with the error message listed above.*

[free4]

This post is deleted!

[opti2k4]

try this:

vi /usr/local/etc/raddb/sites-enabled/default

add following in authorize {} block, restart freeradius

     if (!control:Auth-Type) {
            ldap

            if (ok && User-Password) {
                    update {
                    control:Auth-Type := LDAP
                    }
            }
    }
    expiration
    logintime

Auth server under System - User Manager - Authentication servers must use PAP.

EDIT: on every freeradius config change this gets deleted, so you need to copy/paste and restart freeradius server every time :/.

[free4]

@opti2k4 please have a look go https://forum.netgate.com/topic/140135/how-connect-freeradius-to-ms-ad/8

[opti2k4]

@free4 that works until you make a change on freeradius that causes service to restart. Then added stuff is gone.

There is also another problem, OTP is useless. I can connect to VPN without using OTP even though user is configured with OTP.

[ahmad.rostami]

hi,
Could you solve the problem?
I have the same problem

[free4]

@ahmad-rostami please have a look go https://forum.netgate.com/topic/140135/how-connect-freeradius-to-ms-ad/8

as reminder, freeradius package has been created long time ago by the community.
this package Is mostly legacy and unmaintained nowadays.

if you would like to fix the issues related to this package, feel free to contribute !

[ahmad.rostami]

@free4 Thank you very much for solving my problem
Now how do I prevent reconnection user when finish the quota in captive portal ?

[Gertjan]

@ahmad-rostami said in how connect freeradius to MS AD:

Now how do I prevent reconnection user when finish the quota in captive portal ?

Fill in these settings :

Login :

Jan 7 15:25:20 	logportalauth 	8909 	Zone: cpzone1 - ACCEPT: x, b0:xx:2d:44:fc:da, 192.168.2.5

After a 22 Megabyte download (this exceedings 21 MB ) I'm kicked out :

Jan 7 15:25:59 	logportalauth 	15139 	Zone: cpzone1 - QUOTA EXCEEDED: x, b0:xx:2d:44:fc:da, 192.168.2.5

Now I can login any more ....
I see these logs in the General System logs :

Jan 7 15:30:13 	root 		FreeRADIUS: User x has reached the daily amount of upload and download traffic (22 MB of 1 MB). The login request was denied.

A cron job cleans out the daily totals, so tomorrow (for me : after 12h00) I can re login.

Btw : I'm using the FreeRadius package, and an external 'MariaDB' SQL database.