| Note | ||
|---|---|---|
| ||
Note that this page has been deprecated; the information it contains is no longer current. It has been retained for historical purposes only. |
| Warning |
|---|
After several months of communication with participants, InCommon Operations removed the legacy metadata download endpoint (currently, a redirect) on Wednesday, February 14, 2018 All metadata clients that attempt to download metadata from this endpoint should have switched to one of the production endpoints noted in: Metadata Aggregates before that date. Failure to update to the production metadata locations has likely caused your SAML deployment to break on February 27, 2018 at approximately 2:44 p.m. US Eastern Time. |
For many years, InCommon has supported a redirect from a very old metadata download location:
http://wayf.incommonfederation.org/InCommon/InCommon-metadata.xml
And
https://wayf.incommonfederation.org/InCommon/InCommon-metadata.xml
To the current production (“main”) aggregate location:
http://md.incommon.org/InCommon/InCommon-metadata.xml
On February 14, 2018, InCommon Operations REMOVED this redirect.
It is CRITICAL that all production metadata clients be configured to fetch metadata from http://md.incommon.org/InCommon/InCommon-metadata.xml or one of the other three locations on md.incommon.org.
If you currently fetch metadata from one of the old (wayf.incommonfederation.org) locations noted above, you need to reconfigure your deployment. Failure to do so will mean means that your IdP and/or SPs will break broke on February 27, 2018.
At the bottom of this page, you will find a list of hosts, updated weekly, that are still downloading metadata from the old location. If you see a host on the list that is at your organization, please contact the relevant systems personnel to arrange to switch metadata consumption to one of the supported aggregates.
Please pass along this information to anyone in your organization who is responsible for running an IdP or SP in InCommon, especially those such as delegated administrators or other systems administrators who may not be subscribed to this mailing list.
| Organizations still using Domains with hosts still attempting to use legacy metadata endpoint | |||
|---|---|---|---|
| 1 | acm.org | ||
| 2 | amazonaws.com | ||
| 3 | anlarizona.govedu | ||
| 4 | atg.travel | 5 | atomiclearning.com |
| 65 | berkeley.edu | ||
| 76 | blackboard.com | ||
| 87 | brainerd.net | ||
| 98 | cengage.com | ||
| 109 | cloudtricity.com | ||
| 1110 | cmu.edu | ||
| 11 | co.il | ||
| 12 | code42.com | ||
| 13 | duke.edu | ||
| 14 | eth0-0-fw3-1-ap-q18-va2.mhint | ||
| 15 | eth0-0-fw3-1-ap-r137-3-va3.mhint | ||
| 16 | everestdc.com | ||
| 17 | expedient.com | ||
| 18 | fisc.com | ||
| 19 | fischerinternational.com | ||
| 20 | gatech.edu | ||
| 21 | googleusercontent.com | ||
| 22 | illinois.edu | ||
| 23 | imleagues.com | ||
| 24 | in-addr.arpa | ||
| 25 | internet2.edu | ||
| 26 | iu.edu | ||
| 27 | jhsph.edu | ||
| 28 | jhu.edu | ||
| 29 | kennisnetmbl.orgedu | ||
| 30 | mitmtu.edu | ||
| 31 | mtunorthamericancoax.educom | ||
| 32 | osumc.edu | ||
| 33 | refworks.com | ||
| 34 | rfsuny.org | ||
| 35 | sdstate.edu | 36 | serialssolutions.com |
| 3736 | siteprotect.com | ||
| 3837 | surf.nl | ||
| 3938 | surfnet.nl | ||
| 4039 | t2hosted.com | ||
| 4140 | thomsonreuters.com | ||
| 4241 | trln.org | ||
| 42 | trondent.com | ||
| 43 | trondentts24.com | ||
| 44 | uark.edu | ||
| 45 | uclaucmerced.edu | ||
| 46 | ucmerceducsf.edu | ||
| 47 | ucsf.edu | 48 | ucsfmedicalcenter.org |
| 4948 | uic.edu | ||
| 5049 | uninett.no | ||
| 5150 | utsystem.edu | ||
| 5251 | uw.edu | ||
| 5352 | vizientinc.com | ||
| 5453 | webair.com | ||
| 5554 | whoi.net | ||
| 55 | wm.edu | ||
| 56 | wmwpi.edu |
| Note |
|---|
The information below was last updated on MondayThursday, March 0529, 2018. IMPORTANT: The table on the left is a list of root DNS zones with hosts still attempting to access the legacy metadata location. The table on the right is a list of actual hosts still attempting to access the legacy metadata. REMINDER: When you make a configuration change to target one of the current production metadata aggregate locations, you may need to restart your SAML SP software (shibd/etc) to cause it to re-read the configuration. |