When a new identity federation applies to join eduGAIN, the eduGAIN Secretariat and business development team will work closely with them to help them prepare and meet all the membership requirements. The following steps will be taken and will be used as a template to manage Candidate applications. Each "step" may run concurrently, depending the on the readiness of the federation.
Candidate Name | Federation X |
---|---|
OTRS Ticket Number | TT#2023111534001693 |
eduGAIN New Candidate Process - eduID.tg (the Togo Identity Federation operated by TogoRER)
Steps | Requirements | Actions | Owner | Timeframe | Notes |
---|---|---|---|---|---|
Step 1: Initial application meeting / readiness discussion | This initial meeting will talk the candidate through the joining process, get an understanding of the technical infrastructure of the federation and it's maturity and also share information about useful resources for the federation such as the eduGAIN website and wiki and the REFEDS resources. If not already familiar, federations will also be talked through the available document templates and the various eduGAIN tools that can be used for testing compliance and reviewing issues. |
| BD Sec | Set up meeting within 2 weeks of receiving request | |
Step 2: Collect required information for membership application | There are a number of formalities that need to be addressed before a federation can become a membership candidate. These are known as the "joining checklist" and represent the core information that is held about each federation to enable metadata consumption and to start the trust building process. |
| Sec / OT | TBD - depending on maturity of federation | - Contact email : Laté-Ognadon Chroko LAWSON, rony.lawson@togorer.tg - Security contact : Arnaud AMELINA, rony.lawson@togorer.tg - Governance delegate and deputy : Eyouléki Tcheyi Gnadi PALANGA and Laté-Ognadon Chroko LAWSON - signed eduGAIN Policy Declaration attached to ticket; - federation metadata: https://registry.eduid.africa/signedmetadata/federation/eduid_tg/metadata.xml - metadata signing certificate: (attached to ticket) - Federation website: https://www.eduid.tg - Federation Policy: https://www.eduid.tg/docs/Togo_Identity_Federation_Policy_Document-en.pdf - Federation Metadata Registration Practice Statement: https://www.eduid.tg/docs/MRPS-eduid-tg-v1.1.pdf |
Step 3: eduGAIN Secretariat review of federation documentation | The eduGAIN Secretariat will undertake an initial review of the federation Policy and MRPS documents and may invite others to help support this process. The aim of this step is to help the federation identify any potential issues that might come up from the community review process and ensure step 5 goes as smoothly as possible. |
| Sec | 4 - 6 weeks | |
Step 4: Technical review | The purpose of the technical review is to iron out any issues the federation may have with publishing and consuming eduGAIN metadata on a daily basis to ensure that the federation can run successfully with no / low error rate when membership is approved. |
| Sec / OT | Concurrent with Step 5 & 6 | |
Step 5: membership review of federation documentation | As stated in the eduGAIN Constitution, the eduGAIN Steering Group (eSG) is responsible for: "Reviewing and approving the membership of new Federations". Step 5 and Step 6 support this requirement. |
| Sec | 4 weeks (or 2-3 weeks for assessment + 1-2 weeks for the applicant to process the feedback?) | |
Step 6: voting | Formalised vote for membership acceptance |
| Sec | 2 weeks | |
Step 7: formal registration | This final step ensures that the candidate is able to fully utilise the eduGAIN service after the community vote is successful. |
| Sec |
eduGAIN New Candidate Assessment Feedback
Documents provided | Togo federation. eduID.tg provided docs | URL on the fedederation webpage |
---|---|---|
Togo Fed Policy doc v0.5 - Oct 2, 2023 | https://www.eduid.tg/docs/Togo-Federation-Policy-Document-en.pdf | |
Togo Fed MRPS doc v 1.1 - Oct 2, 2023 |
Assessment Period: DATES
Comment # | Document (Policy / MRPS) | Document line / reference | Proposed Change or Query | Proposer / Affiliation | Reply Candidate |
---|---|---|---|---|---|
#1 | Policy | Section 4&5 | In Section 5 says that all membership applications will be evaluated by the Federation Operator. If this is the case I am not sure if the distinction between accredited R&E institutions (as described in Section 4) and other IdPs/attribute authorities/SPs is necessary. | Casper Dreef / eduGAIN secretariat | Regarding the 1st comment relative to Accredited R&E institutions, this point was made because some institutions might not be accredited by the government R&E regulation authority. But, we can not find other IdPs/attribute authorities/SPs in Section 4&5 in the policy document. |
#2 | Policy | Appendix | This is a copy of the eduID.ng policy. Nigeria is mentioned where it should be Togo. | Casper Dreef / eduGAIN secretariat | Solved |
#3 | Policy/MRPS | general | Please make sure the font is consistent throughout the document. | Casper Dreef / eduGAIN secretariat | Solved |
#4 | Policy | Section 6 Jurisdiction | In the second paragraph, please refer to a specific court of law. | Casper Dreef / eduGAIN secretariat | Solved |
#5 | MRPS | Section 3 | Second paragraph. This is URL linking to the current version of the document. When the policy gets updated, the url changes. This then must be reflected in the MRPS as well. It would be easier to link to a general webpage with an url that is less like to be changed | Casper Dreef / eduGAIN secretariat | Still links directly to the policy document, but this is now the updated version. |
#6 | MRPS | Section 3 | Paragraph 5. Remove () around Ministère de l'Enseignement etc. | Casper Dreef / eduGAIN secretariat | Solved |
#7 | MRPS | Section 6.1 | provide email address / registry tool / other tools | Casper Dreef / eduGAIN secretariat | Solved |
#8 | Metadata | Please provide the metadata URL for the signed metadata. The current link only shows unsigned MD. | Solved: https://registry.eduid.africa/signedmetadata/federation/eduid_tg/metadata.xml |