Migrating to Relying-Party V3
Brent Putman
putmanb at georgetown.edu
Tue Apr 25 12:43:42 EDT 2017
On 4/25/17 12:29 PM, Brent Putman wrote:
>
> *Caused by:
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> bean named 'shibboleth.DefaultEncryptionCredentials' is defined*
>
>
> So sounds like that bean doesn't exist in your conf/credentials.xml.
>
> That bean is defined in the shipped version of the file, so maybe you
> commented some stuff out?
>
Or, if the bean is defined there, then maybe you don't have the
properties idp.encryption.key and idp.encryption.cert defined in
conf/idp.properties? And/or the paths pointed to those don't exist?
By default is:
idp.encryption.key = %{idp.home}/credentials/idp-encryption.key
idp.encryption.cert = %{idp.home}/credentials/idp-encryption.crt
I don't remember off-hand what we do on a v2 upgrade, which didn't
support encryption. Maybe we copy the signing key, but I'm not sure,
one of the other devs on the team probably knows.
It's possible you might have to copy your cert/key (or create a new key
pair and cert) so as to be the encryption credential defined by those
properties. Check your credentials/ folder. (Of course whatever that
cred is, it needs to match what you publish in metadata).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170425/bf04d0a9/attachment.html>
More information about the users
mailing list