Thanks Phil
> 1. For PAP, you can authenticate the user by asking the LDAP module to
> to an LDAP simple bind with the pap username/password
> 2. For MS-CHAP, you install samba, join the domain, and use the
> "ntlm_auth" helper binary in the mschap module
Option 1 is the way things are being han
On Wed, 2007-08-15 at 15:36 +1000, Stewart James wrote:
> What I have realised is that there are 2 ways that authorisation appear
> to be called for LDAP. One way is to name the LDAP modules in the
> authorise section. The other way appears to be through the LDAP-Group
> in the users file and l
gust 2007 1:49 PM
To: FreeRadius users mailing list
Subject: RE: Multiple (different) LDAP servers and authorisation
Hi Alan,
Thanks for offering some help, no need to point out that in reality AD != True
LDAP. Well and truly aware of it.
Lets step through what we need.
At the moment we have a la
, 15 August 2007 12:16 PM
To: FreeRadius users mailing list
Subject: Re: Multiple (different) LDAP servers and authorisation
Stewart James wrote:
> I have been roped in to look over an issue we have with migrating from
> Novell to AD.
Repeat after me: AD is not an LDAP server.
It'
Stewart James wrote:
> I have been roped in to look over an issue we have with migrating from
> Novell to AD.
Repeat after me: AD is not an LDAP server.
It's not. It fakes it pretty well, but it's not.
> As I stated earlier authentication fall through works like a treat (if
> in the users f
5 matches
Mail list logo
