Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: fix mailing lists and formatting

...

If you cannot get such a certificate to send signed emails or if your personal certificate is issued from a CA not listed in the TACAR service, please contact  edugain-ot@geant.net the contact the eduGAIN Operations Team in  in order to establish a different secure communications channel.

...

The eduGAIN Downstream metadata contains all entities in eduGAIN. It is generated and published by the eduGAIN Metadata Distribution Service (MDS) under , see https://mdstechnical.edugain.org/metadata for details.

The downstream metadata is needed because you federation’s entities that are part of eduGAIN should also consume metadata about other eduGAIN entities. Therefore, you as federator operator should provide your entities with that downstream metadata. It is strongly recommended to provide an own version of eduGAIN metadata to your local entities and not directly make them consume from MDS. Consuming eduGAIN metadata directly from MDS is considered bad practice for several reasons. MDS was not built to serve metadata to potentially thousands of entities. Also, you as federation operator lose the ability to filter out eduGAIN entities that for example are not compliant with your federation policy. Furthermore, this might result in conflicts because your entities might load metadata for other eduGAIN entities of your federation twice (once via MDS and once via your local federation’s metadata).

...

...

You can perform the following steps to stay updated with the latest discussions/events:

...

  • Your federation’s deputy and delegate and possibly other key members of the operations team should register to the following mailing lists:

...

...

...

...