Yes, that's what we'd recommend (association of the new IdP metadata
with the old IdP entity ID when you go live, along with removal of old
IdP from metadata). But as already discussed you need to make sure your
new ePTID hash values are the same as the old ones too; I don't know
what kind of control over that you might have with PingFederate.
(We're still waiting for a reply from your management liaison to the
certificate authentication email before we can complete your new IdP
On 10/09/2015 14:35, Todd, James wrote:
> Hi Sara (at al)
> Ok, so thinking of it here: we've just put in a registration for our
> new Ping IdP at the UK Fed helpdesk so in the meantime I'm going to
> have two IdPs registered, albeit the Ping IdP will be hidden until
> we're ready to transition. I assume at this point the EntityID has to
> be unique in the metadata, but when we go live I can drop the old IdP
> and give the new IdP the old entityID?
> Thanks James
> _____________________________________ James Todd | Data Centre &
> Operations Analyst Edinburgh Napier University Craiglockhart Campus
> Edinburgh EH14 1DJ Tel: 0131 455 4313 Email: [log in to unmask]
UK Access Management Federation for Education and Research
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.