Re: After the manual's config, chap wont work with LDAP

Hi all, We've got our freeradius servers working with LDAP fine, except for CHAP. Originally, the logs were saying "Invalid user \\user", but we fixed that by enabling an option in radiusd.conf. Now, when we dial up without encrypted password enabled, the connection comes through successf

Re: After the manual's config, chap wont work with LDAP

To do CHAP, you must have: 1. The PLAINTEXT password in the LDAP server 2. The Radius server permitted to read that attribute 3. The ldap module configured to put whatever that attribute is (usually userPassword) into the radius "User-Passord", using the "password_attribute" option of the

Re: After the manual's config, chap wont work with LDAP

Matt Juszczak wrote: Hi all, We've got our freeradius servers working with LDAP fine, except for CHAP. Originally, the logs were saying "Invalid user \\user", but we fixed that by enabling an option in radiusd.conf. Now, when we dial up without encrypted password enabled, the connection co

After the manual's config, chap wont work with LDAP

Hi all, We've got our freeradius servers working with LDAP fine, except for CHAP. Originally, the logs were saying "Invalid user \\user", but we fixed that by enabling an option in radiusd.conf. Now, when we dial up without encrypted password enabled, the connection comes through successful