"Also sprach Jason Lixfeld:"
> joeuser Login-LAT-Node == FOO
> ARAP-Security-Data = FOO
Well, I think you are right in principle, but it doesn't seem to quite work
for me.
I have
ptb Auth-Type := Local, User-Password == "XXXXXX", Login-LAT-Node ==
User-Security-Data
Fall-Through = Yes
DEFAULT
ARAP-Security-Data = User-Security-Data
And while the user is accepted, all the evidence I can gather so far
seems to show that the STRING "User-Security-Data" is sent back in the
ARAP-Security-Data field. Owww.
I've tried it all in one entry too.
rad_recv: Access-Request packet from host 1.2.3.4:1438, id=245,
length=64
NAS-Identifier = "localhost"
User-Name = "ptb"
User-Password = "XXXXXX"
Login-LAT-Node = "jikxotIX"
Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 0
modcall[authorize]: module "preprocess" returns ok for request 0
modcall[authorize]: module "chap" returns noop for request 0
modcall[authorize]: module "mschap" returns noop for request 0
rlm_realm: No '@' in User-Name = "ptb", looking up realm NULL
rlm_realm: No such realm "NULL"
modcall[authorize]: module "suffix" returns noop for request 0
rlm_eap: No EAP-Message, not doing EAP
modcall[authorize]: module "eap" returns noop for request 0
users: Matched DEFAULT at 159
users: Matched DEFAULT at 221
modcall[authorize]: module "files" returns ok for request 0
modcall: group authorize returns ok for request 0
rad_check_password: Found Auth-Type System
auth: type "System"
Processing the authenticate section of radiusd.conf
modcall: entering group authenticate for request 0
modcall[authenticate]: module "unix" returns ok for request 0
modcall: group authenticate returns ok for request 0
Login OK: [ptb/cacsd1] (from client localhost port 0)
Sending Access-Accept of id 245 to 1.2.3.4:1438
ARAP-Security-Data = "User-Security-Data"
Finished request 0
Going to the next request
And still I can't see what goes out ...
Peter
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
