PAP is not an authorize module though, it must depend on something else for
auth. This is what I have the only other ldap reference is the ldap { config
for rlm } section in the radiusd.conf file and it is a modified version of
the original with no additions.
Users:
DEFAULT Suffix == "@planetez.net"
Service-Type = Framed-User,
Framed-Protocol = PPP,
X-Ascend-Data-Filter = "ip in forward tcp est",
X-Ascend-Data-Filter = "ip in forward dstip 65.216.115.16/32",
X-Ascend-Data-Filter = "ip in drop tcp dstport = 25",
X-Ascend-Data-Filter = "ip in forward",
Fall-Through = Yes
Radiusd.conf
I would guess that is PAP were able to be used here it would solve my
problem (if PAP was a module?)
authorize {
preprocess
chap
ldap
files
suffix
}
authenticate {
chap
pap
}
-----Original Message-----
From: Alan DeKok [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 27, 2002 10:37 PM
To: [EMAIL PROTECTED]
Subject: Re: CHAP-LDAP PAP-LDAP
"Michael S. McCollough" <[EMAIL PROTECTED]> wrote:
> I noticed in radiusd -X that PAP trys to bind to the ldap directory
> where CHAP appears to do a simple search/read The bind status does not
> show up in the debug. Is there a way to make PAP behave like CHAP with
> the ldap module?
Find out where the 'auth-type = LDAP' is being added. Stop it from being
added.
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
