Hi everyone,
I have been using OpenXPKI 1.17 on Debian Jessie as issuing CA and recently
updated to 1.19.4.
Since then my default secret group (realm.ca-one.crypto.secret.default) cannot
be cached in the session anymore.
The crucial setting in crypto.yaml:
secret:
default:
label: Default secret group of this realm
method: plain
cache: daemon -> works vs. ..
cache: session -> breaks
openxpki.log says:
2017/11/21 09:50:50 openxpki.system.ERROR:32521 Mandatory parameter 'value'
missing in call to (eval)
at /usr/share/perl5/MooseX/Params/Validate.pm line 67.
MooseX::Params::Validate::validated_hash(ARRAY(0x4eb27a0), "group",
HASH(0x6fb38e0), "value", HASH(0x6fc8808), "MX_PARAMS_VALIDATE_NO_CACHE", 1)
called at /usr/lib/x86_64-linux-gnu/perl5/5.20/OpenXPKI/MooseParams.pm line 59
eval {...} called at
/usr/lib/x86_64-linux-gnu/perl5/5.20/OpenXPKI/MooseParams.pm line 58
OpenXPKI::MooseParams::named_args(ARRAY(0x4eb27a0), "group", HASH(0x6fb38e0),
"value", HASH(0x6fc8808)) called at
/usr/lib/x86_64-linux-gnu/perl5/5.20/OpenXPKI/Server/Session/Data.pm line 190
(..)
I have noticed, that session handling has changed from 1.17 to 1.19 and have
added "system.server.session.type: File", as advised by the warnings that come
up otherwise.
I also tried out the server.yaml that comes as default with 1.19 and that
stores sessions in the database. This doesn't change the behavior either.
Are there any other settings that must be set with the new session management
or is this possibly a bug?
Thanks in advance,
Dirk
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users
