> rad_recv: Access-Request packet from host 127.0.0.1 port 32772,
>id=96, length=27
> User-Name = "bill"
..
>
>The Access-Request contains a User-Name and plaintext User-Password.
Well, not on debug you posted.
>Is there anything else I can try?
Post the whole debug (server s
Leese, MJ (Mark) wrote:
> 1. Uncomment "set_auth_type = yes" in raddb/modules/ldap. This was
> already done but I think it's the default anyway :-)
Then it should work.
> 2. List "pap" as the last module in the "authorize" section. Sorry, I
> should have said that I'd also tried this. Here is
e userPassword attribute, so I guess this is why PAP also fails to
find a "known good" password?
Is there anything else I can try?
Thanks again,
Mark.
> -Original Message-
> From: Leese, MJ (Mark)
> Sent: 15 March 2009 18:41
> To: 'freeradius-users@lists.fr
Leese, MJ (Mark) wrote:
> In the authorize section FreeRADIUS anonymously binds to our LDAP server
> (Active Directory) and searches for the user identified in the
> Access-Request (in my case we change the default search filter to
> 'sAMAccountName' as our AD doesn't contain 'uid'). If a match is
>I've been successfully using FreeRADIUS 1.1.4 to authenticate users
>against Active Directory using LDAP and a plaintext password.
>
>In the authorize section FreeRADIUS anonymously binds to our LDAP server
>(Active Directory) and searches for the user identified in the
>Access-Request (in my case
Hi,
I've been successfully using FreeRADIUS 1.1.4 to authenticate users
against Active Directory using LDAP and a plaintext password.
In the authorize section FreeRADIUS anonymously binds to our LDAP server
(Active Directory) and searches for the user identified in the
Access-Request (in my case
6 matches
Mail list logo
