The Incommon Federation wiki has moved.

Please visit the new InCommon Federation Library wiki for updated content. Remember to update your bookmarks.

Click in the link above if you are not automatically redirected in 15 seconds.



You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

Interfederation Frequently Asked Questions

These questions and answers are intended to help you understand how eduGAIN will affect your organization and some of the policy questions to be considered.

What is eduGAIN?

eduGAIN collects, aggregates and distributes SAML metadata, enabling collaboration and access to online services globally. The eduGAIN service is operated by GÉANT (in the European Union) for the benefit of the higher ed community worldwide. Participating federations share metadata via the eduGAIN aggregation service, which facilitates SAML interoperability across federation boundaries. 

How does eduGAIN work?

Participating federations (including InCommon) export SAML metadata to eduGAIN. Then eduGAIN combines these metadata files into a single comprehensive aggregate. Participating federations then import the global metadata aggregate from eduGAIN and make that metadata available to their participants.

Why is InCommon participating in eduGAIN?

Research, scholarship and education are increasingly international endeavors. eduGAIN allows researchers, faculty, staff, and scientists to use familiar campus credentials to access collaboration tools and other services from around the world. All types of research projects will benefit from eduGAIN—from small collaborations involving two or three individuals to large government-funded virtual organizations. A major benefit of eduGAIN is that a Service Provider can join just one national federation and provide single sign-on access globally.

From a policy standpoint, what changes will this involve?

The InCommon Participation Agreement (which every InCommon participant has signed) has changed to include language specific to eduGAIN participation. Those changes go into effect on February 11, 2016. You do not need to take any action if you agree with the changes. On November 13, InCommon will provide a policy and legal FAQ that will detail your other choices.

What am I agreeing to by participating in eduGAIN? 

InCommon has published an eduGAIN Intent Statement that outlines the rationale for eduGAIN participation. The document reviews such topics as governance, transparency, policy structure, dispute resolution, and metadata sharing. In general, the policies of their home federations and the laws of their home countries bind all eduGAIN participating organizations. In short, InCommon participants remain under the policies and practices of InCommon, as their home federation.

I’ve read that an expanded attribute release policy is also a consideration. Is that true?

You do not need to change your attribute release policy in order to participate in eduGAIN. However, InCommon recommends that you review your policy and consider supporting the global (REFEDS) Research & Scholarship Category. By doing so, you agree to release a small set of attributes (generally considered directory information) to all Service Providers that have joined the global R&S Category.

Adopting global R&S is intended to make international collaboration seamless for faculty, staff, researchers and scientists, thereby improving interoperability and the user experience.

Where can I learn more about eduGAIN?

The best place to start is www.incommon.org/edugain

My organization operates an Identity Provider. Do you recommend I export my metadata to eduGAIN?

Yes, and in fact, all InCommon Identity Provider metadata will be exported to eduGAIN by default beginning on February 11, 2016. Identity Provider operators will be able to opt out of the export process, if they wish.

My organization operates one or more Service Providers. Do you recommend I export my metadata to eduGAIN?

If you provide a service intended to have global reach, we recommend that your Service Provider metadata be exported to eduGAIN. Service Provider owners will be able to opt into the export process, if they wish.

For example, a campus researcher may host a wiki or a database or some other service that needs to be available to colleagues in other countries. We recommend exporting that Service Provider to provide single sign-on convenience to international collaborators.

If you are with a company that provides a service globally, we recommend that you export that SP. If a service is strictly US-only, we recommend you not export your metadata – you will continue to be included in the InCommon metadata aggregate.

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels