As we already run FR for other reasons, I'm considering making it our site server for Eduroam, and proxying to NPS for local authentications. Unfortunately NPS is not too good as a proxy server either, and I could just give myself problems with local use of Eduroam (which we have a lot of). Trouble is, NPS is very good at Windows authentication, and the combination of FR EAP and Samba is a lot for our support staff to get their heads round
Regards
Max
Sent from my iPhone
On 27 Jun 2013, at 17:58, "Alan Buxey" <[log in to unmask]> wrote:
> One day NPS might support Status-Server packets. The NPS is already marking the NRPS (incorrectly) as dead (is the remote site that's the problem as the NRPS rejects are saying) of NPS supported Status-Server them it'd know better. I don't have any power/influence on Microsoft to update and upgrade the RADIUS RFCs it supports.... customers using NPS should get some traction on this. Explain the case and business case. .. point them to the RFCs (and whilst you're there ask them to support adding attributes to outbound proxied packets so that NPS can support Operator-Name and CUI request.....)
>
> alan
>
--
Scanned by iCritical.
|