AW: Sealer issue

[Franz, Fabian]

Yes that fixed the sealer warning / error.

used this command to generate a new one and it worked immediately. If anyone has the same issue, this is the command I used:
keytool -keystore credentials/sealer.jks -alias secret1 -keypass redacted -storepass redacted -storetype JCEKS -genseckey -keyalg aes -keysize 256

It still has an error but I will create a different discussion for that as it is likely unrelated.
________________________________
Von: Cantor, Scott <cantor.2 at osu.edu>
Gesendet: Montag, 16. September 2024 14:38
An: Shib Users <users at shibboleth.net>
Cc: Franz, Fabian <Fabian.Franz at alpegagroup.com>
Betreff: Re: Sealer issue

WARNING: This email originated from outside of the Alpega Group. Do not click links or open attachments unless you recognize the sender and know the content is safe.


I would make sure it's not just a persmission issue.

> I tried to open the keytore in KSE (Keystore Explorer;
> https://keystore-explorer.org/) and it seems to run into the
> same issue.

I don't know that that handles secret key files. If it did and you got the error, then clearly the password's just wrong.

Blow the files away and start over, the seckeygen command line should be able to create a new one.

-- Scott


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20240917/01509f48/attachment.htm>