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 | YAMI |
|---|---|
| OTRS Ticket Number |
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 | edugain- discuss list still not done |
| 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 | |
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
Policy Doc and MRPS - December 2024: here
Policy document + MRPS: https://www.redconare.ac.cr/wp-content/uploads/2024/11/YAMI-en.pdf
| Comment # | Document (Policy / MRPS) | Document line / reference | Proposed Change or Query | Proposer / Affiliation | Reply candidate |
|---|---|---|---|---|---|
| #1 | Policy: Section 1 | Definitions and terminology: Digital identity. | The D&T of digital identity is spread over two lines / mentioned twice. This D&T should be combined | Casper Dreef/GÉANT | Fixed |
| #2 | Policy: Section 1 | D&T: Community identify community | What does this mean? | Casper Dreef/GÉANT | Fixed, original document said Federation identity federation, that is why we replicated the error. Now is: Community of Identity Communities |
| #3 | Policy: Section 1 | D&T: Inter-community | Do you mean Inter-federation? | Casper Dreef/GÉANT | We mean inter-community |
| #4 | Policy: | General comment | It seems like Federation is wrongfully translated to Community throughout the document. | Casper Dreef/GÉANT | We had to use the term "community" instead of "federation" . The use of the term "federation" in our country is associated with an entity composed of multiple associations registered with the National Registry. All these entities are governed by Private Law. The federation's statutes must also be registered in the same manner. |
| #5 | Policy: S3.3 | Must ensure its IT systems that are used in implemented Technology Profiles are operated securely. Must pay the fees. | It seems like two bullets were combined. Also, I couldn't find anything on the YAMI website about fees for YAMI members. How is this processed? | Casper Dreef/GÉANT | here are no fees, It will be an agreement among the parties. We are working on it. |
| #6 | Policy S3.5 | Bullet 3&4 | Should be a separate sub-section as it is about Service Providers, not Attribute Authorities. | Casper Dreef/GÉANT | Fixed |
| #7 | Policy S4 | 3rd paragraph | I would advise to remove this section. In case a foreign entity requests becoming a member, I would redirect them to RedCLARA's federation FIEL. | Casper Dreef/GÉANT | The paragraph is now removed |
| #8 | Policy S4 | 5th paragraph: To become a member of Yami FIEL Identity Community as a Service Provider only | Remove FIEL | Casper Dreef/GÉANT | FIEL removed |
| #9 | General | "How to join" section is missing on the federation webpage | Casper Dreef/GÉANT | This will be added soon. This will also include a description of the applicable fees (see comment #5) |