Holiday Technology Checklist 2016
ANNOUNCEMENT: Reduced Metadata Signing Operations
Mark your calendars! The Internet2 offices will be closed from 5:00pm ET, Friday, December 23, 2016 to 8:00am ET, Tuesday, January 3, 2017. No metadata processing will occur during this interval except during the following two days:
NOTE: Metadata processing and signing will occur on Wednesday–Thursday, December 28–29, 2016 at approximately 12:30pm ET! No other metadata signings are scheduled during the holiday period!
See the published InCommon Hours of Operation for more information.
You may want to add these items to your holiday shopping list
- Choose the best metadata aggregate for your SAML deployment
- Configure all your SPs to consume the IdP-only aggregate
- Configure your test IdPs to consume the preview aggregate
- Production IdPs should continue to rely on the main aggregate
- Upgrade to Shibboleth IdP V3 now! (Version 2 reached end-of-life on July 31, 2016)
- For a list of IdPs that have (or have not) upgraded to V3, see: List of Shibboleth IdPs by Version (ref)
- Note: Shibboleth IdP V3.3.0 was announced on November 11, 2016
- Support the global Research & Scholarship Category!
- Information for SP owners wanting to apply for R&S
- Information for IdP operators who release attributes to R&S SPs
- See: List of Global Research and Scholarship Entities (ref)
- Support the InCommon Federated Error Handling Service!
- Add an Error Handling URL (ref) (
errorURL
) to IdP metadata - To check if your
errorURL
is working properly, see: List of errorURLs in IdP Metadata - Add an administrative contact (ref) in IdP metadata
- Add an Error Handling URL (ref) (
- Is your IdP discoverable?
- Tweak your IdP DisplayName in metadata (if necessary)
- Add a Logo URL to IdP metadata (and publish a favicon on your IdP server)
- Learn more about the Hide From Discovery Category
- Migrate to the REFEDS security contact
- Touch your metadata to convert the InCommon security contact to the REFEDS security contact
- For a list of entities that include a legacy InCommon security contact, see: List of Legacy Security Contacts
- Harden your IdP server
- Analyze the TLS configuration of your IdP server using SSL Labs
- Scan your IdP server using the Observatory by Mozilla