Update username attribute in NAS

[Anirudh Malhotra]

Hi,

@Padam and magically when I recreate the access-request from NAS after 
receiving the first access accept+username from FR, and when I again 
receive the same reply from FR this time my cisco NAD takes the username 
:D haha , I have opened a TAC lets see what they have to say for this :P

BR,
Anirudh Malhotra


On Wednesday 09 December 2015 02:55 PM, Anirudh Malhotra wrote:
> Hi Padam,
>
> Thanks a lot for your email.
>
> But I have a question it is written it "MAY" be optionally sent by 
> Radius, correct? . If in case it is sent NAS "SHOULD" comply with it 
> and use that for all the accounting packets followed. Am I correct?
>
>
> Also I am sending it in update reply { }, which is being sent with 
> access accept. So is it possible that access accept(which I dont know 
> what is inside it) may be sending the old username only?
>
> BR,
> Anirudh Malhotra
>
> On Wednesday 09 December 2015 01:57 PM, Padam Jeet Singh wrote:
>>> On 09-Dec-2015, at 10:58 am, Anirudh Malhotra 
>>> <amalhotra.sp-dl at nkn.in> wrote:
>>>
>>> Hey Everyone,
>>>
>>> I have few questions first:
>>> Can User-Name attribute be updated at NAS after authentication is 
>>> completed(post auth)?
>>  From RFC 2865:
>> 5.1.  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.*
>>
>> So your NAS does not comply - it doesn’t need to because it’s not a 
>> MUST.
>>
>> Your best bet may be the Class attribute. It’s sent verbatim back to 
>> server in most NAS.
>>
>> Padam
>>
>>
>> -
>> List info/subscribe/unsubscribe? See 
>> http://www.freeradius.org/list/users.html
>