Well,
I've reached a few conclusions here, and according to the following log I can
deduce the
following:
Cleaning up request 253 ID 35 with timestamp 469a18da
Sending Access-Reject of id 36 to 192.168.2.80 port 47588
Waking up in 4 seconds...
rad_recv: Access-Request packet from host 192.168.2.80:47589, id=37, length=194
User-Name = "[EMAIL PROTECTED]"
Digest-Attributes = 0x0a05313031
Digest-Attributes = 0x010e3139322e3136382e322e3830
Digest-Attributes =
0x022a34363961323238356338303335366239633531383533353961623933373332303364333931366635
Digest-Attributes = 0x04127369703a3139322e3136382e322e3830
Digest-Attributes = 0x030a5245474953544552
Digest-Response = "1c40cdddbc1dafeaea453f1f2a726e15"
Service-Type = Authenticate-Only
X-Ascend-PW-Lifetime = 0x313031
NAS-Port = 5060
NAS-IP-Address = 192.168.2.80
Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 255
perl_pool: item 0xa459b10 asigned new request. Handled so far: 8
found interpetator at address 0xa459b10
rlm_perl: RAD_REQUEST: X-Ascend-PW-Lifetime = 0x313031
rlm_perl: RAD_REQUEST: Digest-Response = 1c40cdddbc1dafeaea453f1f2a726e15
rlm_perl: RAD_REQUEST: User-Name = [EMAIL PROTECTED]
rlm_perl: RAD_REQUEST: Service-Type = Authenticate-Only
rlm_perl: RAD_REQUEST: NAS-IP-Address = 192.168.2.80
rlm_perl: RAD_REQUEST: NAS-Port = 5060
rlm_perl: RAD_REQUEST: Digest-Attributes = ARRAY(0xa592764)
perl_pool total/active/spare [32/0/32]
Unreserve perl at address 0xa459b10
modcall[authorize]: module "perl" returns ok for request 255
modcall: leaving group authorize (returns ok) for request 255
auth: No authenticate method (Auth-Type) configuration found for the request:
Rejecting the user
auth: Failed to validate the user.
Login incorrect: [EMAIL PROTECTED]/<no User-Password attribute>] (from client
openser port 5060)
Delaying request 255 for 1 seconds
Finished request 255
Going to the next request
It would appear the the autorization portion of the process works just fine,
and is being negotiated
via the rlm_perl module. However, it would appear that the authentication
portion isn't even transfered
to the handling of the rlm_perl module for some reason. I've gone over various
information I can find,
in regards to the usage of Auth-Type settings for rlm_perl, however, all have
produced the same result
at the above.
If any one has information at this point, this would be highly appreciated.
z2l
----- Original Message -----
From: "Alan DeKok" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], "FreeRadius users mailing list"
<freeradius-users@lists.freeradius.org>
Sent: 14:52:19 (GMT+0200) Asia/Jerusalem יום שלישי 17 יולי 2007
Subject: Re: RLM_PERL Integration Issue
FreeRadius-ML wrote:
> Well, right now I would like to start of with something really simple. I'd
> like to have OpenSER authenticate
> on FreeRadius, Digest is not a must - for all I care at this point, it can be
> clear-text. I'm currently using
> the perl script example from the FreeRadius website, which if i understand
> correctly, should answer OK on any
> request to it. That is what I where i want to get to at this point, once that
> is working, i can continue onwards.
You are trying to do two independent things at the same time.
1) get Digest authentication working.
2) Get Perl working.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
