Add test shibboleth metadata to InCommon metadata file

[Michael A Grady]

> On Aug 20, 2015, at 7:20 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> 
> On 8/20/15, 7:59 PM, "users on behalf of John Kamminga" <users-bounces at shibboleth.net on behalf of jkamminga at ucmerced.edu> wrote:
> 
>> I have a test instance of Shibboleth IdP v2.4.2 running and would like to add the metadata to the InCommon metadata file so I can test with some SPs.
>> 
>> 
>> Do I just upload the shib test X.509 certificate to the InCommon Federation Manager and then add it to my existing production metadata? Or, do I need to have a separate metadata entityId in the InCommon Metadata file?
> 
> That's not a totally well-defined question because "testing" can mean a lot of different things, but generally speaking there is no reason to test an IdP that way. You can emulate your existing IdP top to bottom and use local /etc/hosts changes to do your testing, as long as the back channel isn't involved.
> 
> -- Scott
> 

And you can't register a 2nd IdP with InCommon unless you want to spend extra dollars:

  https://spaces.internet2.edu/display/InCFederation/Test+IdPs+in+Metadata

But as Kevin Foote noted, you really want to check with InCommon administration to get the official answers, through your InCommon Site Admin and/or Exec.

--
Michael A. Grady
IAM Architect, Unicon, Inc.