IdP 3.0.0.11 to 3.1.0.1 upgrade issue

[Dave Bartholomew]

Shibboleth 3.1.0.1 64-bit

Windows Server 2012 R2

java version "1.8.0_31" (Oracle JDK)



Shibboleth installed in C:\Program Files (x86)\Shibboleth via installer
(install Jetty checked).



"Working" is defined as https://localhost/idp/profile/status returns data
as opposed to a "Service Unavailable" error (503).



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.



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

metadata-providers.xml

relying-party.xml

attribute-resolver.xml

ldap.properties



Stopped working after I updated conf (not subdirs) with the remaining dist
files:

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



I was expecting it to work.

Any ideas on what went wrong?



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.



Thanks.



Dave Bartholomew

Cal State University, East Bay

ITS

Dave.Bartholomew at csueastbay.edu

(510) 885 – 2324
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20150313/635aa61d/attachment.html