Hi Nick,
OpenXPKI supports so called "Signer On Behalf" so in case you are
managing those certs from a central location it might be worth to just
have ONE authentication certificate to sign the end-entity requests but
in the end this will also have the same "password issue" :(
As sscep is an
Hi,
> Thank you very much for the reply, I was wondering because the config did not
> change and everything worked smooth before the upgrade.
The semantics I posted have been in place and unchanged for a very long time,
and we did not change the relevant code portions recently, so the cause mig
Thank you very much for the reply, I was wondering because the config did
not change and everything worked smooth before the upgrade.
I'll try the proposed configuration.
___
OpenXPKI-users mailing list
OpenXPKI-users@lists.sourceforge.net
https://lists.
Hi,
> We are using docker containers. At webui.log:
>
> 2023/05/19 08:34:20 ERR Error creating backend client Error while writing to
> socket; __EVAL_ERROR__ => I18N_OPENXPKI_CLIENT_INIT_CONNECTION_FAILED;
> __ERROR__ => Permission denied, __SOCKETFILE__ =>
> /var/openxpki/openxpki.socket [pid
Hi Oliver,
I’ve tried the same enrollment process but this time I switched to « log_level
= TRACE » in the configuration of OpenXPKI (scep/default.conf) so that I can
collect more information.
FYI: router configuration:
crypto pki trustpoint TEST_PKI
enrollment retry count 3
enrollment retry p
