This is an old revision of the document!


Onboarding

Q: We're a public sector organisation and would like to join Govroam, what are the next steps?

A: Contact govroam@jisc.ac.uk and you'll be sent all the appropriate documentation for joining.

The Full Boarding form needs filling out completely. It asks for contact information, information about your RADIUS servers and for a letter of consent from someone senior e.g:

"Dear Sir/Madam,

Re: Govroam

Please accept this letter as authority of behalf of <insert organisation here> for the provision of the Govroam service over our network infrastructure as a full member.

Your faithfully,

<Director of IT>"

scan it to a PDF and send it to govroam@jisc.ac.uk.

Submit the form back to us, and then we'll sort out the appropriate payments, shared secrets for RADIUS servers, access to the CAT, the Govroam App, subscribe you to the support mailing lists and add your support details to our Support Matrix.

Q: We're a public sector organisation and would like to join Govroam as a Visited Only site, what are the next steps?

A: Contact govroam@jisc.ac.uk and you'll be sent all the appropriate documentation for joining.

The Visited Only Boarding form needs filling out completely. It asks for contact information, information about your RADIUS servers and for a letter of consent from someone senior e.g:

"Dear Sir/Madam,

Re: Govroam

Please accept this letter as authority of behalf of <insert organisation here> for the provision of the Govroam service over our network infrastructure as a Visited Only site.

Your faithfully,

<Director of IT>"

scan it to a PDF and send it to govroam@jisc.ac.uk.

Submit the form back to us, and then we'll sort out the shared secrets for RADIUS servers, the Govroam App, subscribe you to the support mailing lists and add your support details to our Support Matrix.

Q: We're a University/Third Party that wants to implement Govroam as a Visited Only service. What do we have to do?

A: There are three things to do:

  1. Take your existing eduroam configuration, duplicate the part of it related to visitors, change the 'eduroam' bits to 'govroam'. So that should cover the SSID, 802.1x setting on your wireless controllers, a VLAN to put the visitors on, an address range for them, firewall settings (same as eduroam). Then the RADIUS config should be able to send unknown realms to our NRPS.
  2. Download the Visited Only Boarding form, fill it out and send it back to govroam@jisc.ac.uk.
  3. Have your Director of IT (or someone suitably senior) write a brief letter of authorisation along the lines of
"Dear Sir/Madam,

Re: Govroam

Please accept this letter as authority of behalf of <insert institution here> for the provision of the Govroam service over our network infrastructure as a Visited Only site.

Your faithfully,

<Director of IT>"

scan it to a PDF and send it to govroam@jisc.ac.uk.

Then we'll send you the details (shared secrets and addresses) for our NRPS for you to configure in your RADIUS servers. We'll include a test account so that you can confirm that outgoing authentication requests work and we have a web page through which you can test incoming authentication requests. We'll sign you up to a technical mailing list and give you access to our Wiki of relevant information.

This documentation is related:

Tech Spec V2

Technical

Q: What's the relationship between Govroam and eduroam? Do I need one to have the other or do I have to have both?

A: They're very closely related but they aren't the same and there are no dependencies either way. eduroam has been around for years in the academic sector and is mature. Govroam uses exactly the same idea and technology but is aimed at NHS, Local Government and other public sectors. JISC runs the top level RADIUS servers for both services but they are completely separate.

Thus it's possible to have neither, either or both.

If you already run eduroam (i.e. a University) then adding Govroam is easy (and free). Essentially you need to duplicate your wireless and RADIUS configurations and request the shared secret details from JISC.

Q: Which should I have?

A: This very much depends upon the sort of users you have at your site. The services have concepts of Home and Visited:

Home is where a user has their credentials stored/generated (e.g. a University for an eduroam user or an NHS Trust for a Govroam user. At a Home site there will be a wireless system, RADIUS servers and a credential store (e.g. Active Directory).

Visited is where the user roams to and wants to work from. A Visited site will have a wireless system and RADIUS servers.

Now a site can be one or the other, or both. And that goes for both services. (Although it would be rare to have a Home only site).

Typical scenarios:

  • A University: Home and Visited for eduroam. Visited only for Govroam. A University might want to offer connectivity to NHS staff visiting from the Teaching Hospital next door.
  • A Hospital: Home and Visited for Govroam. Visited only for eduroam. A Hospital could have medical students on site and want to offer them connectivity.

In both these scenerios there might be people who work for both the University and a Hospital. In which case they could have two sets of credentials or just credentials from one side. At either the Hospital or the University they could still connect with either set.

  • Reseller: Visited for eduroam and Govroam. They want to be able to offer the connectivity to their customers when on their site.

So ask yourselves “What sort of users to we want to offer services to?”. If you're a public sector employer then you'd want to be Home and Visited for Govroam. If you've got academic types on site then consider offering Visited for eduroam. If you're a University then you can offer Visited Govroam alongside your eduroam install for free.

Q: What hardware/software is required for Govroam?

A: As much or as little hardware as you want/Any RADIUS server.

A full service requires a wireless system, RADIUS and a network connection to the Internet. Assuming that you have the former and the latter then the RADIUS hardware is fairly simple. RADIUS software doesn't use much in the way of resources. e.g. A Raspberry PI running RadSecProxy could handle dozens of requests per second and would be functional for a medium sized enterprise - although not recommended! Any modern rack mount server, or a VM with a couple of CPU, a couple of GB of memory and 10GB of storage would be more than adequate for a top level RRPS or ORPS.

If you already have a RADIUS server then you may be able to configure it to act as an ORPS at no extra cost. If the software doesn't allow it, or you want to separate your services then the ORPS you add will only be handling the authentication requests destined/source to/from offsite, which will by about 1% of your total authentication requests.

As for the software - any modern RADIUS server can handle Govroam. There are no odd requirements. Having said that through, there should be a preference for servers which can handle Server Status (for resilience), CUI (Chargeable User Identity for audit), Operator-Name (for logging) and RADSEC (for the future).

If you value the service then resilience should be considered. At least two RADIUS servers at each level are recommended and three is quite common. Many RADIUS servers (and wireless controllers) offer load balancing options so hardware load balancers shouldn't be needed. The servers themselves are generally stateless and require no intercommunication.

Q: How much does the hardware/software cost to run Govroam RADIUS on?

A: Following on from the above question: between zero and a lot. If you have a spare piece of hardware, or can create a VM at no cost then installing a linux variant and FreeRADIUS would cost nothing. As would adding the ORPS capability to an existing RADIUS configuration. If you have to buy hardware then £500-1000 should cover the cost of a suitable Dell server. If you want to purchase RADIUS software such as Clearpass then you'll have to talk to a reseller as the licences can be complex. Even a reasonably sized hospital ought to be able have something for under £5,000 though. The final costs with depend on a number of factors which are site specific.

Q: What do I do with users once they're authenticated?

A: You can make this as simple or as complex as you wish. There is a minimum service level associated with govroam but it's not particularly restrictive. At the simplest level govroam Visitors to your site need a network segment separate from other users, a basic set of open ports (such as web and VPN) and some bandwidth.

Note 'govroam visitors'. If you're using govroam for your own people on your own site then you can treat them differently (put them on a VLAN/firewall context which has less restrictive firewalling or more access to local services, for example).

A common approach is to use a RADIUS attribute, set by the ORPS, to identify the user as a Visitor and set an appropriate role on the wireless system/firewall.

Q: What EAP types can we use?

A: Easy one: any. The slightly longer answer is that any data in the inner tunnel is encrypted so is completely independent of the outer tunnel. As long as the outer tunnel has the right 'routing information' i.e. the realm, then the proxying will work. Thus each site can be using a different EAP type and it should all work. The use of PEAP is very common, EAP-TLS less so but plenty of sites use it successfully.

Q: Would you be able to provide direct support with setting up and running our RADIUS system?

A: Jisc can provide a variety of different sorts of help at various levels and there are plenty of options outside of Jisc.

Jisc can:

  1. Provide high level documentation covering how federated authentication works and the technical requirements
  2. Work with sites during the onboarding phase
  3. Offer onsite, paid, consultancy if sites are using particular RADIUS software (FreeRADIUS, radsecproxy, Clearpass).
  4. Attempt to put sites in contact with Federations with suitable experience or Universities prepared to offer help.

Jisc isn't in a position to recommend external consultants or commercial third party partners, however, there are several companies who are able to offer these services and are currently doing so for both Govroam and eduroam. They should also be able to offer ongoing support.

Joining with an existing Federation has the benefits of potential significant reductions in boarding fees as well as access to people in your area and your field with existing experience of configuring Govroam.

Jisc has experience with RADIUS software such as FreeRADIUS and radsecproxy so can offer full configuration support as well as limited configuration advice on Clearpass.

Virtually all Universities have been using eduroam from many years so have significant experience and are often very willing to help others. They may not have much time to spare though and experience limited to the common eduroam RADIUS platforms, such as FreeRADIUS and Cisco ISE.

Jisc is able to provide a test account and some tools for external testing of credentials. We will work with sites until the boarding is complete and authentication works through the proxies.

Q: Which RADIUS server should we use?

A: Jisc aren't allowed to recommend particular RADIUS servers. The ones we're aware of that meet all the requirements of our Technical Spec are

  • FreeRADIUS (open source, linux),
  • radsecproxy (open source, linux),
  • RADIATOR (commerical, linux and Windows),
  • Aruba Clearpass (commerical, appliance).

radsecproxy is purely a proxy whereas the others can also integrate with data stores for authentication. Other RADIUS servers may also meet the requirements.

Q: As a Federation what process should we follow when Onboarding sites?

A:

  1. For each site gather the details of their RADIUS server(s), realm(s) and a technical contact. This would include IP address(es)/hostname(s), non standard ports, any load balancing and whether they support Status Server.
  2. Configure your RRPS for the above, generating suitable shared secrets. The configuration should, obviously, include the client/server information to allow communications between RADIUS servers and suitable routing of the realms.
  3. Share these shared secrets and the details of your RADIUS server with the site technical contact, securely.
  4. The site should then configure their end.
  5. RFO should then provide Jisc with the following information about the site (This is all put onto our wiki and made available to all sites for troubleshooting, incident and audit purposes):
    1. Realm(s)
    2. Name and location of the site
    3. Name, position, email and phone number of the technical contact for the site
    4. Help desk (website, phone number, openings times) for the site.
  6. The site can then test outgoing connectivity either using credentials supplied by the Federation, or the ones provided by Jisc. Incoming connectivity can be tested using the website provided by Jisc with local site credentials.
  7. The site is provided with a login to Jisc's App site so that they can populate Govroam locations on a map.