IdP 3.0.0.11 to 3.1.0.1 upgrade issue

[Cantor, Scott]

On 3/13/15, 2:32 PM, "Dave Bartholomew" <Dave.Bartholomew at csueastbay.edu> wrote:

>Had 3.0.0.11 working with some 2.x configuration manually migrated over.
> 
>Updated to 3.1.0.1 (in place) and it stopped worked, but daemon was still running.

That's a bug, so all we can do is take a detailed bug report and follow up.

> 
>"Fixed" it by overwriting all my modified files (which had some problems) with 3.1.0.1 dist files:

There is absolutely nothing that should have worked in 3.0.0 and then broken, so we need to know what it was that stopped working.

>2015-03-12 12:33:33,558 - ERROR [org.springframework.web.context.ContextLoader:331] - Context initialization failed
>Cannot resolve reference to bean 'shibboleth.DataSealer' while setting bean property 'dataSealer'
>Exception loading the default key
>Keystore was tampered with, or password was incorrect

That probably means what it says, so I have to think you must have overwritten the idp.properties file containing the keystore password you supplied during installation with a value that was no longer right. Or something like that. There is a default value in the distribution but it's meaningless, it has to be set by the initial installer and not changed unless the sealer keystore is manually edited or replaced.

You should never just overwrite your files with anything new. You can diff them if you like to compare them to the defaults, but your changes should be left in place. Anything new will be for new features and have appropriate default behavior, so it's never mandatory to bring in new settings on an upgrade.

>I'm trying to figure out the best update strategy - starting "clean" with everything (presumably) working with the (perhaps new) defaults and then copy in my modified files after checking for any differences or doing a simple in place update and then going backwards making changes and fixing deprecated things, etc. If I can find out what happened, it might influence my approach.

You MUST do the latter. It is not going to work to start clean because you will almost certanly end up failing to pull in your changes reliably. That was how V2 worked and it didn't work.

-- Scott