add new IDP metadata with InCommon wizard?

[Cantor, Scott]

> Some of our folks have test Shib SPs, which
> are configured to use the test IDP via the test entityID.  I'll need to talk to
> them about using the production entityID and local /etc/hosts instead.

If you really intend to run two IdPs for public consumption, then practically speaking they're both "public", and you would have to discuss it with InCommon. Discovery is one of the basic challenges with doing that.

If you have local systems you want to support, then you can publish your own metadata for that, you don't need InCommon to do it (I don't really recommend using InCommon to publish your metadata on campus anyway, that's only needed for SPs that are actually federated).

I don't personally believe in this model, I think systems need clear boundaries that preclude test -> test -> test flows end to end, because you're basically doubling your entire infrastructure and coupling everybody's testing together, and you end up needing a third IdP for development by you. But my own people argue with me about that endlessly, and they have settled on refusing to support test accounts in our IDM system, so it's a stalemate.

-- Scott