Sealer key error...

[Marc SAHIN]

Exactly, the webapp context doesn't initialize.
I've created a new sealer.jks and there is no secret key error anymore.
I notice just that there is an info log like "/Key not found/" but no 
client side issue.

/2017-06-30 09:23:27,126 - INFO 
[net.shibboleth.utilities.java.support.security.BasicKeystoreKeyStrategy:289] 
- Key 'secret55' not found//
//2017-06-30 09:23:27,127 - INFO 
[net.shibboleth.utilities.java.support.security.DataSealer:218] - Data 
was wrapped with a key (secret55) no longer available/

Is there any way to correct it or can it be ignored ?

Thank you for your help.

Best regards,

Marc SAHIN
Administrateur Systèmes
Pôle Système  - DSI - Université Lumière Lyon 2
04 78 77 26 66

On 29/06/2017 18:39, Cantor, Scott wrote:
>> However, I can't start Tomcat because of password of Sealer.jks
> Tomcat doesn't know anything about it, I assume you mean the webapp context just doesn't initialize.
>
>> Is it possible to recreate the keystore from scratch ?
> The seckeygen script/command can start one from scratch as well as rolling the key, and it has a help list of parameters.
>
>> Can it be caused client side error ?
> No.
>
> -- Scott
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170630/a8039877/attachment.html>