Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The contact information concerning the Identity Provider in the eduroam Operations Database MUST be complete and accurate, including at least email address, postal address and telephone number
  • The Identity Provider MUST generate Chargeable-User-Identity attributes in authentication responses
  • The DNS zone for the Identity Provider's realm name MUST include a NAPTR record for their realm pointing to an eduroam OpenRoaming interchange proxy. The example below targets the general-purpose proxy operated by eduroam OT; the target host may be different for eduroam NROs who operate their own proxy:

    realm.name. 43200 IN NAPTR 100 10 "s" "aaa+auth:radius.tls.tcp" "" _radsec._tcp.openroaming.eduroam.org.

  • End user devices need to be provisioned with the pertinent settings to recognise OpenRoaming hotspots - see section "End-User Device Settings" below
  • The end users themselves need to be made aware that they are bound by the OpenRoaming End-User Terms and Conditions whenever they connect to OpenRoaming hotspots.
  • If using NPS as the RADIUS server for password-based authentication, you *must* add the user 'anonymous' into your Active Directory instance, but you can disable it (it must merely exist). Recent versions of Android will use the word 'anonymous' followed by your realm name as the so-called Outer Identity for tunnelled methods (such as EAP-TTLS or PEAP), and NPS will reject any authentication attempts from Android devices if the 'anonymous' user cannot be found in Active Directory. 

When your user is actually roaming with OpenRoaming, this is visible in the RADIUS datagrams due to the RADIUS Attribute

...