Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 NameFederation X
OTRS Ticket Number

TT#2023013134001556

eduGAIN New Candidate Process

StepsRequirementsActionsOwnerTimeframeNotes
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.

  •  Organise meeting with federation, eduGAIN Secretariat, eduGAIN BD and other relevant parties
  •  Add federation to edugain-discuss mailing list and eduGAIN Slack workspace
  •  Ensure a formal ticket is open for the federation application in OTRS
  •  Set up candidate profile on wiki to track progress

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.


https://technical.edugain.org/joining_checklist

  •  Contact email
  •  Security contact
  •  Management contact
  •  Signed declaration
  •  Metadata source
  •  Signing certificate
  •  Governance delegate and deputy
  •  Federation website
  •  Federation policy
  •  Federation MRPS
  •  Contact OT to add federation as a candidate on the eduGAIN website
Sec / OTTBD - depending on maturity of federation

Documents at: https://geant.box.com/s/ip0h2b6lm4xmsxdpb9e7x6bks3yvp07o


1. Contact email:
contact@federasi.id ; bsi@uii.ac.id
 
2. Security contact:
Agus Setiawan: agus.setiawan@uii.ac.id 
UII-CSIRT: abuse@uii.ac.id
 
3. Signed-declaration
 
4. Metadata
Production Metadata: https://jagger.federasi.id/signedmetadata/federation/IndonesiaAccessFederation/metadata.xml
 
Signing Certificate: https://federasi.id/metadata/fedsigner.pem
 
SHA1 fingerprint: 11:43:2E:95:F5:E7:03:41:EE:C1:09:50:00:62:58:83:3F:BD:53:C1 
SHA256 fingerprint: E2:43:CF:08:9F:F5:8E:C3:F3:8F:8A:96:3A:21:13:00:1D:C0:24:27:8C:86:C7:B9:16:90:3B:70:FD:75:27:1E
 
5. Governance delegate and deputy
- Delegate: Mukhammad Andri SETIAWAN (andri@uii.ac.id)
- Deputy: Pandu Bangun ASMORO (pandu@uii.ac.id)
 
6. Federation page
https://federasi.id
 
7. Policy
Attached
or https://federasi.id/federation-policy/
 
8. Registration practice statement
Attached
or https://federasi.id/metadata-registration-practice-statement/

Attached 

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.
  •  Undertake review of federation documentation
  •  Initial feedback from the eduGAIN Secretariat on documentation review
  •  Organise meeting to discuss feedback if appropriate

Sec


4 - 6 weeks
Step 4: Technical reviewThe 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.
  •  Work with OT to ensure certificate is correct
  •  Review of metadata against validator checks
  •  federation metadata should run with no errors for the period of time taken to complete the candidate assessment
Sec / OTConcurrent with Step 5 & 6
Step 5: membership review of federation documentationAs 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.
  •  Announce review on edugain-discuss and edugain-sg mailing lists
  •  Invite comments to made on appropriate wiki page
  •  Run review process for a period of 4 weeks
Sec4 weeks (or 2-3 weeks for assessment + 1-2 weeks for the applicant to process the feedback?)
Step 6: votingFormalised vote for membership acceptance
  •  Prepare vote in Zeus
  •  Prepare voting record page on wiki
  •  Run vote for period of 2 weeks
Sec2 weeks
Step 7: formal registrationThis final step ensures that the candidate is able to fully utilise the eduGAIN service after the community vote is successful.
  •  Liaise with OT to update federation from candidate to member
  •  Add federation to edugain-sg mailing list
  •  Add federation to eduGAIN reporting tool
Sec

eduGAIN New Candidate Assessment Feedback

Assessment Period: DATES

Comment #Document (Policy / MRPS)Document line / referenceProposed Change or QueryProposer / Affiliation
#1MRPSSection 4Under 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

#2MRPSSection 5.1refers to https://federasi.id/becoming-a-member on how to register a service but that only describes membership appliance.

Pål Axelsson/SWAMID

#3MRPSSection 6.1talks 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

#4PolicySection 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

#5PolicySection 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