(RADIATOR) Accounting Requests (DLG-24)

[Frank Danielson]

As Hugh already mentioned these are requirements that should be met by your
NAS but if that is not possible you could track the User-Name using the
Class attribute.

The User-Name attribute could be copied to the Class attribute in a
ReplyHook for the auth requests and then a PreAuthHook would be used to copy
the Class attribute to the User-Name attribute on incoming Accounting
requests.

Frank Danielson
Infrastructure Architect

ClearSky Mobile Media
56 E. Pine St.
Orlando, FL 32801
USA

fdanielson at juno.com

-----Original Message-----
From: Ajay Gopinath [mailto:Ajay.Gopinath at ttiadvant.com]
Sent: Tuesday, August 09, 2005 9:57 PM
To: Hugh Irvine
Cc: radiator at open.com.au; jira
Subject: (RADIATOR) Accounting Requests (DLG-24)


 
Hi Hugh, 
We are using "AuthBy Radius" authentication. The other radius server sends
back a Access-Accept packet with a user name attribute. We need to use this
user name for all Account Requests made by us for this session.
Following is a description of the scenario 
User-Name: 
This Attribute indicates the name of the user to be authenticated. 
It MUST be sent in Access-Request packets if available. 
It MAY be sent in an Access-Accept packet, in which case the 
client SHOULD use the name returned in the Access-Accept packet in 
all Accounting-Request packets for this session. If the Access- 
Accept includes Service-Type = Rlogin and the User-Name attribute, 
a NAS MAY use the returned User-Name when performing the Rlogin 
function. 
Cheers, 
Ajay 

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.