okay.....so MSCHAPv2 etc are very fussy. my assumption here would be that in your proxy.conf, for the 'moco' realm, you havent got 'nostrip' defined.. so user-name is getting altered. this really plays merry games with end authentication systems that use that as part of the hashing etc. define that realm as 'nostrip' and then you should see 'test-user@moco' being sent off as User-Name to 172.20.192.19 and it will work.
Alan Buxey .thanks for the reply. But i can`t create user account with symbol "@" in my billing system. Please help. how can I fix this problem with ms-chapv2 ?
Hi,
okay.....so MSCHAPv2 etc are very fussy. my assumption here would be that in your proxy.conf, for the 'moco' realm, you havent got 'nostrip' defined.. so user-name is getting altered. this really plays merry games with end authentication systems that use that as part of the hashing etc. define that realm as 'nostrip' and then you should see 'test-user@moco' being sent off as User-Name to 172.20.192.19 and it will work.
Alan Buxey .thanks for the reply. But i can`t create user account with symbol "@" in my billing system. Please help. how can I fix this problem with ms-chapv2 ?
proxy the accounting and strip the user-name in that proxy - that way you deal with usernames properly and the accounting can be safely not fed the '@' character (which we just escape along with other chars into a PSQL DB) alan
participants (2)
-
Alan Buxey -
Влад Власов