Unable to access DataSealer from Spring context on IdP-511

[Francesco Malvezzi]

good morning,

I realized that a command that used to work out-of-the-box on IdP-341:

$ bin/sealer.sh conf/totpsealer.xml enc data
INFO  - Loading initial default key: totp3
INFO  - Default key updated to totp3
AAV0b3RwMz2vM0HEB6Do7ROUeIGwA7HGn7dijIMRlci1jeRf0svC51wpVd4TxRAaFZA6gPeqSS7X9FeElg4whYWDNA==

now on IdP-511, I have an issue:

$ bin/sealer.sh conf/totpsealer.xml enc data
INFO  - Including auto-located properties in 
/opt/shibboleth-idp/conf/ldap.properties
INFO  - Including auto-located properties in 
/opt/shibboleth-idp/conf/saml-nameid.properties
INFO  - Including auto-located properties in 
/opt/shibboleth-idp/conf/c14n/subject-c14n.properties
INFO  - Including auto-located properties in 
/opt/shibboleth-idp/conf/services.properties
INFO  - Including auto-located properties in 
/opt/shibboleth-idp/conf/authn/SpidExternal.properties
INFO  - Including auto-located properties in 
/opt/shibboleth-idp/conf/authn/X509External.properties
INFO  - Including auto-located properties in 
/opt/shibboleth-idp/conf/authn/authn.properties
INFO  - Including auto-located properties in 
/opt/shibboleth-idp/conf/admin/admin.properties
ERROR - Unable to access DataSealer from Spring context

part of the problem is logging: on shibboleth-idp4 it spelled out 
detailed error messages whether either the resource 
(conf/totpsealer.xml, in this example) or the JKS or the kver file were 
missing.

Now it is no longer talkative and error message is just "ERROR - Unable 
to access DataSealer from Spring context".

I am working on Debian GNU/Linux 12 (bookworm),
$ echo $SHELL
/bin/zsh

The sealer usage example is taken from: 
https://shibboleth.atlassian.net/wiki/spaces/IDPPLUGINS/pages/1376878877/TOTP

Any debugging hint is appreciated!

thank you,

Francesco