Shib IdP v3: Which certificate do you upload to InCommon?

[Karla Borecky]

Indeed, we did have to make adjustments - esp.  with some of the changes in
V3. Still having problems with a few here and there, ones that I had to
exchange 100 emails with (not an exaggeration) to get them set up and
working in the first place. :-P

Thanks, everyone!

Karla

ps I kind of wish we could just upload our metadata file to InCommon
instead of feeding them the component bits. But I guess I understand why
they do it that way.

On Mon, Mar 14, 2016 at 3:52 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> > * Karla Borecky <kborecky at smith.edu> [2016-03-14 20:00]:
> > > Well, we brought up a new IdP, with new certs and a new entityID.
> >
> > Then there's nothing to change wtih regards to your existing/old IDP,
> > and you register the new IDP with InCommon the same way everyone
> > registers IDPs with InCommon.
>
> I actually overlooked the "new entityID" part. Obviously that's not a key
> rotation, then, it's just a new IdP entirely. Any SP you're working with is
> effectively starting from scratch, so there are any number of outside
> considerations here. They might have to make database changes, or any
> number of adjustments on their side, for you to completely change to a new
> IdP.
>
> -- Scott
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>



-- 
Karla Borecky
Systems Administrator
ITS
Smith College
Northampton, MA 01063
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20160314/ec196602/attachment.html>