I'll try to answer the LDAP question here.
Here's the short answer: make sure the ldap module is removed from the authenticate section, and make sure the mschap module is present in both the authorize and the authenticate section. And just ignore the 'No "known good" password'.
And now here's the (very) long answer.
How does the ldap module work?
When you activate the ldap module in the authorize section, this is what it does when a RADIUS packet is received by FreeRADIUS:
- it tries to bind to the LDAP server (as a guest user, or using the given identity if one is configured in
ldap.conf)
- it searches for the user's DN entry using the filter under the base DN (configured in
ldap.conf).
- it fetches all the LDAP attributes it can get among those configured in
ldap.attrmap, and converts them into RADIUS Attributes.
- it adds those attributes to the RADIUS packet's check items list.
When you activate the ldap module in the authenticate section, this is what FreeRADIUS does:
- it tries to bind to the LDAP server as the user.
- if it can bind, then it's a successful authentication, and a
Radius-Accept packet will be sent back to the client, or else, it's a failure, leading to a Radius-Reject packet.
So how can I configure FreeRADIUS to make PEAP/MS-CHAP-v2 work with LDAP?
The important point here is that binding as the user will only work if the FreeRADIUS server can retrieve the cleartext password of the user from the RADIUS packet it received. This is only the case when PAP or TTLS/PAP authentication methods are used (and possibly also EAP/GTC). Only the TTLS/PAP method is really secure, and it is not available by default in Windows. If you want your users to connect with TTLS/PAP, you need to have them install a TTLS supplicant software, which is seldom an option. Most of the time, when deploying WiFi with WPA Enterprise securiy, PEAP/MS-CHAP-v2 is the only reasonable option.
So the bottom line is: unless you are using PAP or TTLS/PAP, you can safely remove the ldap module from the authenticate section, and actually, you should: binding as the user will not work.
If your test works when you use radtest, it probably means that the ldap module is activated in the authenticate section: it will try to bind as the user, and since radtest uses PAP authentication, it will succeed. But it will fail if you try to connect through the access point, since you are using PEAP/MS-CHAP-v2.
What you should do is remove the ldap module from the authenticate section, and make sure you activate the mschap module in both the authorize and the authenticate section. What will happen is that the mschap module will take care of authentication using the NT-Password attribute which is retrieved from the LDAP server during the authorize phase.
Here is what your sites-enabled/default file should look like (without all the comments):
...
authorize {
preprocess
suffix
eap {
ok = return
}
expiration
logintime
}
authenticate {
eap
}
...
And here is what your sites-enabled/inner-tunnel file should look like:
...
authorize {
mschap
suffix
update control {
Proxy-To-Realm := LOCAL
}
eap {
ok = return
}
ldap
expiration
logintime
}
authenticate {
Auth-Type MS-CHAP {
mschap
}
eap
}
...
What about the 'No "known good" password' warning?
Well, you can safely ignore it. It's just there because the ldap module could not find a UserPassword attribute when it fetched the user details from the LDAP server during the authorize phase. In your case, you have the NT-Password attribute, and that's perfectly fine for PEAP/MS-CHAP-v2 authentication.
I guess the warning exists because when the ldap module was designed, PEAP/MS-CHAP-v2 did not exist yet, so the only thing that seemed to make sense at the time was to retrieve the UserPassword attribute from the LDAP server, in order to use PAP, CHAP, EAP/MD5 or such authentication methods.
Best Answer
I will take a crack at this.
Group DN Pattern. This is forcing you to put all of your groups into one ou (Organizational Unit) on your LDAP server. So you will need to have them in one location and make the pattern reflect that. Say for instance all of your groups are in ou=pgina,ou=groups,dc=mydomain,dc=com and your groups use cn for naming in their DN. Then your group DN pattern would be "cn=%g,ou=pgina,ou=groups,dc=mydomain,dc=com".
For member attribute normally the attribute would by "member" if it is looking for the member's DN but if it just looking for their uid then "memberUid" will work.
For authentication with LDAP best practice is to search based on userid and then retrieve the DN and not to statically generate a DN. So you will want to select "Search for DN" and then your search filter should be "(&(uid=%u)(objectClass=person))". Your search contexts will be the top level of your ldap tree where you want to start searching for users. If they are all in one ou say ou=users,dc=mydomain,dc=com then that would be your context.
For reference DN is Distinguished Name and it is an absolute reference to a user within an LDAP server. You can use an LDAP browser to look at entries and look at either the entrydn or distinguishedname attribute (depending on server) to see what an entries distinguished name is.