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#2023013134001556 |
eduGAIN New Candidate Process
| 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 | Documents at: https://geant.box.com/s/ip0h2b6lm4xmsxdpb9e7x6bks3yvp07o 1. Contact email: |
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
Assessment Period: DATES
| Comment # | Document (Policy / MRPS) | Document line / reference | Proposed Change or Query | Proposer / Affiliation |
|---|---|---|---|---|
| #1 | MRPS | Section 4 | Under section 4 there should be written in the text that their registration authority in metadata I https://federasi.id/. As it is right it’s only mentioned in the non-normative example | Pål Axelsson/SWAMID |
| #2 | MRPS | Section 5.1 | refers to https://federasi.id/becoming-a-member on how to register a service but that only describes membership appliance. | Pål Axelsson/SWAMID |
| #3 | MRPS | Section 6.1 | talks about entity change and section 5.1 about adding entities. Here is a duplicate due to that in 6.1 they also talks about adding entities. Easiest is to remove “entity addition” in section 6.1 | Pål Axelsson/SWAMID |
| #4 | Policy | Section 3.1 | I read it as this talks about the “FEDERASI management body”. However, last sentence in the first paragraph and in the introduction to bullet list it only says “FEDERASI” and in the bullet list I find things that may be part of the management body and federation operator responsibilities. I may be reading this wrongly, but I think there needs to be a clearance on that. I also see that the management body is answerable to the federation operator I the first paragraph, that sounds odd. In section 3.2 it’s well stated that the operator is reporting to the management body. | Pål Axelsson/SWAMID |
| #5 | Policy | Section 4 | Elsewhere in the document three parties are described: home organisations, attribute authorities and service providers. In Section 4 "attribute authorities" is missing. | Pål Axelsson/SWAMID |