Hi Martin,
I had left the notification and metadata handling at default - hadn't
touched them since initial setup, and was getting this error. I then tried
setting up the smtp backend, but I may not have done it correctly. I'll
start digging into the notification handling, as that does seem to be where
it's getting tripped up.
Here is the technical log from the GUI (the dns lookup failing is expected,
this was just a test cert):
2023-12-21 21:18:39 UTC INFO Trigger notification message csr_created
([undef])
2023-12-21 21:18:39 UTC INFO Set datapool entry: key = RE:DA:CT:ED,
namespace = certificate.privatekey ([undef])
2023-12-21 21:18:33 UTC INFO Policy DNS check failed on 1 items ([undef])
2023-12-21 21:18:33 UTC INFO Check DNS policy on these items: test ([undef])
2023-12-21 21:18:33 UTC INFO Rendering subject:
CN=test,DC=internal,DC=the-sprawl,DC=org ([undef])
and here is the snippet of openxpki.log from inside the docker container
when I hit 'resume' on the workflow:
2023/12/22 13:42:01 ERROR Workflow
4863/certificate_signing_request_v2/NOTIFY_CSR_PENDING uncaught exception
[pid=29|role=RA
Operator|sid=6RUz|rid=564c63cfcd38|wftype=certificate_signing_request_v2|wfid=4863]
2023/12/22 13:42:01 ERROR I18N_OPENXPKI_SERVER_WORKFLOW_ERROR_ON_EXECUTE;
__ACTION__ => csr_notify_pending, __ERROR__ => requested value is not a
scalar at /usr/share/perl5/Connector/Builtin/Memory.pm line 74, <DATA> line
1.
at /usr/share/perl5/OpenXPKI/Server/API2/Plugin/Workflow/Util.pm line 318.
, __EXCEPTION__ => [pid=29|role=RA
Operator|sid=6RUz|rid=564c63cfcd38|wftype=certificate_signing_request_v2|wfid=4863]
2023/12/22 13:42:01 ERROR I18N_OPENXPKI_SERVER_WORKFLOW_ERROR_ON_EXECUTE;
__ACTION__ => csr_notify_pending, __ERROR__ => requested value is not a
scalar at /usr/share/perl5/Connector/Builtin/Memory.pm line 74, <DATA> line
1.
at /usr/share/perl5/OpenXPKI/Server/API2/Plugin/Workflow/Util.pm line 318.
, __EXCEPTION__ => [pid=29|role=RA
Operator|sid=6RUz|rid=564c63cfcd38|wftype=certificate_signing_request_v2|wfid=4863]
and here is a snippet of my notification/smtp.yaml:
backend:
class: OpenXPKI::Server::Notification::SMTP
host: smtp.gmail.com
# FQDN for helo - defaults to system fqdn
#helo: my.own.fqdn
port: 587
starttls: 1
username: busiek.maximill...@gmail.com
password: <REDACTED>
debug: 0
# You need to install MIME::Tools for html support
use_html: 0
everything else in smtp.yaml was copied from
democa/notification/smtp.yaml.sample
Let me know if there's anything else I can provide that would be of help
troubleshooting this issue. Appreciate your assistance!
Thanks,
Max
On Fri, Dec 22, 2023 at 2:51 AM Martin Bartosch via OpenXPKI-users <
openxpki-users@lists.sourceforge.net> wrote:
> Hi Maximillian,
>
> > Having some trouble with a new openxpki install using the docker image.
> I've gotten most everything configured, but when I try to generate a CSR
> via the webui, I get the following error:
> >
> > Unexpected error
> > This workflow was interrupted by an unexpected event, it will not
> continue without a manual interaction. Please contact the support team!
> > Last Update
> > 2023-12-21 21:18:39 UTC
> > Failed Action
> > csr_notify_pending
> > Exception Message
> > requested value is not a scalar at
> /usr/share/perl5/Connector/Builtin/Memory.pm line 74. at
> /usr/share/perl5/OpenXPKI/Server/API2/Plugin/Workflow/Util.pm line 318.
> >
> > I've tried swapping out the profile I'm using with the tls_server.yaml
> profile in the democa and that has the same issue. I've also swapped out
> the default.yaml with the one from the democa and still, same issue. Not
> sure what else I can set to default configs to get this working, but any
> help would be appreciated.
>
> From the GUI error message you posted something is not correctly
> configured with regard to notification.
>
> Reading between the lines of your post I assume you did a certain amount
> of customization, possibly involving notification or metadata handling.
> However, without additional information such as technical log, log file
> contents and relevant configuration snippets it is unfortunately not
> possible to provide any assistance.
>
> Cheers
>
> Martin
>
>
>
> _______________________________________________
> OpenXPKI-users mailing list
> OpenXPKI-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openxpki-users
>
_______________________________________________
OpenXPKI-users mailing list
OpenXPKI-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openxpki-users
