JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for JISC-SHIBBOLETH Archives


JISC-SHIBBOLETH Archives

JISC-SHIBBOLETH Archives


JISC-SHIBBOLETH@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

JISC-SHIBBOLETH Home

JISC-SHIBBOLETH Home

JISC-SHIBBOLETH  September 2015

JISC-SHIBBOLETH September 2015

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Migrating to a new IdP

From:

"Haynes, Jonathan" <[log in to unmask]>

Reply-To:

Discussion list for Shibboleth developments <[log in to unmask]>

Date:

Thu, 10 Sep 2015 09:15:52 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (206 lines)

Ignore everything I wrote - I've just realised you said you are going to use PingFederate not the Shibboleth IDP.

Time for another cup of coffee!

Sorry for the noise.

--
-------------------------------------------------------------------------------------
                                    Jonathan Haynes 
                               Senior Network Specialist

IT Department                              Tel: 01234 754205
Bld 63,                                         e-mail: [log in to unmask] 
Cranfield University,
Cranfield,
Beds, MK43 0AL


> -----Original Message-----
> From: Discussion list for Shibboleth developments [mailto:JISC-
> [log in to unmask]] On Behalf Of Haynes, Jonathan
> Sent: 10 September 2015 10:10
> To: [log in to unmask]
> Subject: Re: Migrating to a new IdP
> 
> I think you might be able to get around this problem with the StoredID
> connector.   This stores the persistent identifiers in a database which you
> could manipulate.
> 
> This is completely untested so I could be wrong!
> 
> 1.    On your current IDP set up StoredID instead of ComputedID
> 2.    By default it creates identifiers in the same way as ComputedId so your
> users will get the same values (assuming you use the same salt) but these
> will be stored for future use.
> 3.    Take the database from the old IDP, change all the values in the local
> entity column to your new entity ID and install on the new IDP.
> 4.    Your existing users will get the same persistent ids read from the
> database. New users and existing users going to a new (to them) SP will get a
> newly created persistent id using the standard algorithm and the new
> entityID.
> 
> 
> It may be that you consider the solution worse than the problem. You have
> to maintain a database as well as your shib IDP so there are more moving
> parts. And you will have to maintain this database going forward - it isn't just
> something to be used during the transition  (Only if all your existing users
> finish, or you drop access to all SPs with personalisation that you currently
> use can you return to using ComputedID). If you have HA or a server farm for
> your IDPs then all need to see the same database and you need database
> replication etc.
> 
> And if you are needing to run both IDPs in parallel they both need to
> read/write the same database.
> 
> Like others I would say try to avoid changing your entity id but this is just a
> suggestion for personalisation issues if you really have to.
> 
> 
> Jonathan
> 
> --
> -------------------------------------------------------------------------------------
>                                     Jonathan Haynes
>                                Senior Network Specialist
> 
> IT Department                              Tel: 01234 754205
> Bld 63,                                         e-mail: [log in to unmask]
> Cranfield University,
> Cranfield,
> Beds, MK43 0AL
> 
> 
> > -----Original Message-----
> > From: Discussion list for Shibboleth developments [mailto:JISC-
> > [log in to unmask]] On Behalf Of Sara Hopkins
> > Sent: 09 September 2015 19:45
> > To: [log in to unmask]
> > Subject: Re: Migrating to a new IdP
> >
> > Hi James,
> >
> > Further to what my colleague Steve said here; yes, if your entity ID
> > changes then your eduPersonTargetedID / persistent-id values will
> > change and all (not almost all, but all!) your Digimap users will need
> > to re-register and will lose access to work they have saved in their old
> > profiles. The same is true for other SPs with personalisation features.
> >
> > So I would strongly recommend that (if it is possible to do so) you set
> > up the software so that the hash value component of the ePTID/persistent
> > ID remains the same for all your (user, SP) pairs, and that the entity
> > ID of the new IdP when it goes into production is the same as the
> > current production entity ID.
> >
> > Regards,
> >
> > Sara Hopkins
> > UK federation support team
> >
> > On 09/09/2015 17:49, Steve Glover wrote:
> > > Hi James,
> > >
> > > We don't have specific guidance for this case, but the page we have for
> > > IdP operators moving from hosted to local solutions may give you some
> > > idea of the potential bumps and potholes in the road ahead:
> > >
> > > http://www.ukfederation.org.uk/content/Documents/OAMDtoLocalIdP
> > >
> > > As to how the various SPs handle a change on the IdP side, "it depends":
> > > some will need to be told specifically, some may be able to permit use
> > > of old and new IdPs during the changeover if you ask them, some won't
> > > seem to mind (or perhaps care) and some will take longer than others to
> > > pick up that a change has happened at all.
> > >
> > > One good bit of news: you won't need to tell DigiMap you've changed
> > > entityID: it cares more about the scope. However, changing your entityID
> > > will mean that your eduPersonTargetedID / persistent-id values will
> > > change and almost all your DigiMap users will need to re-register.
> > > losing any saved resources in the meantime - so you may need to keep
> the
> > > old IdP running in parallel with the new one for some time.
> > >
> > > Hoping this is useful,
> > >
> > > Steve
> > >
> > >
> > > On 09/09/15 16:59, Todd, James wrote:
> > >> Hi All
> > >>
> > >> We're currently setting up a PingFederate IdP cluster to replace our
> > >> ADFS\Shib 2.3\Novell Access Manager mish-mash of an SSO solution
> and
> > >> my attention has turned to the UK Federation portion of things.
> > >>
> > >> One of the challenges I forsee is getting the new EntityID out to all
> > >> the SPs our students and staff may use. There are a couple of SPs in
> > >> the federation which are there specifically for us and I'll contact
> > >> them of course, but for the rest (your DigiMaps, JSTOR etc) that's
> > >> going to be a lot of SPs for me to contact.
> > >>
> > >> Anybody who has gone through an IdP migration recently: what
> approach
> > >> have you taken to a smooth transition? Are there a known list of SPs
> > >> perhaps who really check the EntityID of the IdP, and are there some
> > >> who are satisfied with the IdP just being in the federation metadata?
> > >>
> > >> This may seem like a silly question, but I'm just looking for a way to
> > >> avoid a long drawn out manual process for hundreds of SPs...
> > >>
> > >> 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]<mailto:[log in to unmask]>
> > >>
> > >> ** IT Support is now available 24 hrs a day, 365 days of the year **
> > >>
> > >> For Help and Advice on any of our IT services please visit:
> > >> Staff Intranet:
> > >> http://staff.napier.ac.uk/services/cit/Pages/info-services.aspx
> > >> Student Portal:
> > >> https://studentportal.napier.ac.uk/citservices/default.aspx
> > >>
> > >> [CSE logo 2014]
> > >>
> > >>
> > >> This message and its attachment(s) are intended for the addressee(s)
> > >> only and should not be read, copied, disclosed, forwarded or relied
> > >> upon by any person other than the intended addressee(s) without the
> > >> permission of the sender. If you are not the intended addressee you
> > >> must not take any action based on this message and its attachment(s)
> > >> nor must you copy or show them to anyone. Please respond to the
> > sender
> > >> and ensure that this message and its attachment(s) are deleted.
> > >>
> > >> It is your responsibility to ensure that this message and its
> > >> attachment(s) are scanned for viruses or other defects. Edinburgh
> > >> Napier University does not accept liability for any loss or damage
> > >> which may result from this message or its attachment(s), or for errors
> > >> or omissions arising after it was sent. Email is not a secure medium.
> > >> Emails entering Edinburgh Napier University's system are subject to
> > >> routine monitoring and filtering by Edinburgh Napier University.
> > >>
> > >> Edinburgh Napier University is a registered Scottish charity.
> > >> Registration number SC018373
> > >>
> > >>
> > >
> >
> >
> > --
> > Sara Hopkins
> > Support Team
> > UK Access Management Federation for Education and Research
> > web:    http://www.ukfederation.org.uk/
> >
> > The University of Edinburgh is a charitable body, registered in
> > Scotland, with registration number SC005336.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
June 2019
May 2019
March 2019
February 2019
January 2019
November 2018
July 2018
June 2018
May 2018
April 2018
March 2018
January 2018
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
March 2016
February 2016
January 2016
December 2015
November 2015
September 2015
August 2015
June 2015
April 2015
March 2015
February 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager