Child pages
  • Holiday Technology Checklist 2016

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.

Skip to end of metadata
Go to start of metadata


Note that this page has been deprecated. The information it contains is no longer current.

2016 Holiday Technology Checklist for InCommon Site Administrators

Mark your calendars now! The Internet2 offices will be closed from 5:00pm ET, Thursday, December 22, 2016 to 8:00am ET, Tuesday, January 3, 2017. Reduced metadata processing will occur during this holiday period as follows:

Reduced Metadata Signing Schedule

NOTE WELL! Metadata processing and signing will occur on Wednesday, December 28, 2016 at approximately Noon ET! No other metadata signings are scheduled during the holiday period!

See the published InCommon Hours of Operation for more information.

Scheduled maintenance on the Federation Manager

The server hosting the InCommon Federation Manager will be unavailable due to maintenance on Tuesday, December 27, 2016 between 8:00am and Noon ET. The actual maintenance procedure will only take 30 minutes but InCommon Operations reserves the entire 4-hour window for this maintenance operation. Please plan ahead!

You may want to add these items to your holiday shopping list   (smile)

  1. Upgrade to Shibboleth IdP V3 now!
    1. Shibboleth IdP V2 reached end-of-life on July 31, 2016
    2. For a list of IdPs that have (or have not) upgraded to V3, see: List of Shibboleth IdPs by Version
    3. TIP: Shibboleth IdP V3.3.0 was announced on November 11, 2016
  2. Support the global Research & Scholarship Category!
    1. Information for SP owners wishing to apply for R&S
    2. Information for IdP operators wanting to support R&S SPs
    3. See: List of Research and Scholarship Entities as of 1/27/2017
  3. Support the InCommon Federated Error Handling Service!
    1. Add an Error Handling URL (errorURL) to your IdP metadata
    2. To check if your errorURL is working properly, see: List of errorURLs in IdP Metadata
    3. Add an administrative contact to IdP metadata (see: Contacts in Metadata)
  4. Migrate to the REFEDS security contact
    1. Simply touch your metadata ("Edit" => "Save" => "Submit") to convert an existing security contact to the new REFEDS syntax
    2. To check if your metadata includes a legacy security contact, see: List of Entities with Legacy Security Contacts
  5. Is your IdP discoverable?
    1. Tweak your IdP DisplayName in metadata (if necessary)
    2. Add a Logo URL to IdP metadata (and publish a favicon on your IdP server)
    3. Learn more about the Hide From Discovery Category
  6. Harden the TLS configuration on your IdP server
    1. Analyze the TLS configuration of your IdP server using SSL Labs
Happy Holidays and Seasons Greetings! from everyone at InCommon/Internet2
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels