in radiusd.conf:
ldap {
server = "1.2.3.4"
basedn = "o=Company, c=NL"
filter = "uid=%u"
dictionary_mapping = ${raddbdir}/ldap.attrmap
timeout = 4
timelimit = 3
net_timeout = 1
ldap_debug = 0x0000
}
authenticate {
ldap
}
authorize {
ldap
}
and in 'users':
DEFAULT Auth-Type := LDAP
Fall-Through = Yes
Most other features you of course can comment out. It is kinda handy to put
the IP address in the 'server' field else you'll end up getting the ldap
module to resolve the damn thing at every request.
-Peter
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 15, 2001 10:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Failed to validate the user...
"Brendan Holmes" <[EMAIL PROTECTED]> wrote:
> > You've got 'files' commented out, so you're not using the 'users'
> >file. That may have something to do with the problem.
>
> The above configuration is the only one it works for me with out core
> dumping :( I've tried lots of different combinations in the authorize
> scope.
I just ran the server with a bounds checking compiler. I didn't use
the LDAP or SQL modules, but in all of the other ones, there were no
memory leaks, or read/write errors to bad memory.
So the main server core appears to be OK.
Hmm... does anyone have quick hints for setting ldap up? I just
noticed that one of our QA machines has ldap, and I may be able to run
the bounds checking/memory checking compiler on that. In which case,
any memory leaks in the ldap module should show up quickly.
Alan DeKok.
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
