This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
public:faq [2018/07/13 12:34] admin |
public:faq [2019/05/17 06:58] admin |
||
---|---|---|---|
Line 7: | Line 7: | ||
A: Contact < | A: Contact < | ||
- | The {{ :public:171005_gov011_govroam_full_boarding_form_v2.0.docx |Full Boarding | + | The {{ :public:20180815_full_boarding_v3.0_gov011.docx |full boarding |
- | < | + | Once we have properly completed forms 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. |
- | "Dear Sir/ | + | |
- | + | ||
- | 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, | + | |
- | + | ||
- | < | + | |
- | </ | + | |
- | + | ||
- | scan it to a PDF and send it to < | + | |
- | + | ||
- | 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?=== | ===Q: We're a public sector organisation and would like to join Govroam as a Visited Only site, what are the next steps?=== | ||
Line 29: | Line 15: | ||
A: Contact < | A: Contact < | ||
- | The {{ :public:170921_gov012_govroam_visited_only_form_v2.0.docx |Visited Only Boarding form}} needs filling out completely. It asks for contact information, | + | The {{ :public:20180820_visited_boarding_v3.0_gov012.docx |Visited Only Boarding form}} needs filling out completely. It asks for contact information, |
< | < | ||
Line 47: | Line 33: | ||
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. | 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 that wants to implement Govroam as a Visited Only service. What do we have to do?=== | + | ===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: | A: There are three things to do: | ||
- Take your existing eduroam configuration, | - Take your existing eduroam configuration, | ||
- | - Download the {{ :public:170921_gov012_govroam_visited_only_form_v2.0.docx |Visited Only Boarding form}}, fill it out and send it back to < | + | - Download the {{ :public:20180820_visited_boarding_v3.0_gov012.docx |Visited Only Boarding form}}, fill it out and send it back to < |
- | - Have your Director of IT (or someone suitably senior) write a brief letter of authorisation along the lines of | + | - Have your Director of IT (or someone suitably senior) write a brief letter of authorisation, on corporate headed paper, |
< | < | ||
"Dear Sir/Madam, | "Dear Sir/Madam, | ||
Line 161: | Line 147: | ||
* Aruba Clearpass (commerical, | * Aruba Clearpass (commerical, | ||
radsecproxy is purely a proxy whereas the others can also integrate with data stores for authentication. Other RADIUS servers may also meet the requirements. | 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: | ||
+ | - For each site gather the details of their RADIUS server(s), realm(s) and a technical contact. This would include IP address(es)/ | ||
+ | - Configure your RRPS for the above, generating suitable shared secrets. The configuration should, obviously, include the client/ | ||
+ | - Share these shared secrets and the details of your RADIUS server with the site technical contact, securely. | ||
+ | - The site should then configure their end. | ||
+ | - 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, | ||
+ | - Realm(s) | ||
+ | - Name and location of the site | ||
+ | - Name, position, email and phone number of the technical contact for the site | ||
+ | - Help desk (website, phone number, openings times) for the site. | ||
+ | - 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. | ||
+ | - The site is provided with a login to Jisc's App site so that they can populate Govroam locations on a map. | ||
+ | |||
+ | This {{ : |