Skip to Content.
Sympa Menu

metadata-support - [Metadata-Support] IdP Version 3 InCommon Metadata Migration

Subject: InCommon metadata support

List archive

[Metadata-Support] IdP Version 3 InCommon Metadata Migration

Chronological Thread 
  • From: "Kelly, Kyle E" <>
  • To: "''" <>
  • Subject: [Metadata-Support] IdP Version 3 InCommon Metadata Migration
  • Date: Wed, 13 Jan 2016 19:26:24 +0000
  • Accept-language: en-US

First, let me state that I am new to shibboleth and was not involved in the University of South Dakota’s original InCommon Federation. I will try my best not to come off as ill informed, here goes… How difficult is it to change the entityID with InCommon when migrating to a new IdP server? I was recently put in charge of upgrading and migrating to a new server running Shibboleth Identity Provider v3. I currently have a working version of IdPv3, but the entityID of the new IdP server is different than the previous. I am preparing to migrate the InCommon Federation to our new server and I’ve noticed that it is recommended to not change the entityID.


Also, how do I ensure that the new metadata will support SAML 2.0? I believe our current InCommon federation is one of a handful that does not support SAML 2.0.


I am in the process of migrating other service providers to this new IdP server. We currently only use one SP (Cayuse) with our InCommon federation. Let me know if there is any other information I can provide.


Kyle Kelly

System Software Specialist

Information Technology Services

The University of South Dakota

Vermillion, SD  57069


Archive powered by MHonArc 2.6.16.

Top of Page