The config setup looks good so I have no idea what the problem is, you
might want to run lintconfig as openxpki user to double check if this
can read the files, too.
I dont know where you git the Raspian packages from anf how old they
are, perhaps they are too old to handle this syntax - to move forward
you can just add the names of the reports to the workflow instead of
using the reference structure..
Am 04.04.21 um 02:19 schrieb Mitch Mitchell:
Here are the protection attributes:
/etc/openxpki/config.d/realm#
drwxr-xr-x 15 openxpki openxpki 4096 Mar 25 02:04 magnoliaca
./magnoliaca/report:
total 8
-rw-r--r-- 1 openxpki openxpki 382 Mar 18 22:53 expiry.yaml
-rw-r--r-- 1 openxpki openxpki 114 Mar 18 22:53 valid.yaml
Output of lintconfig:
root@muffin:/etc/openxpki# openxpkiadm lintconfig
Checking config at /etc/openxpki/config.d/
Config ok (99d309eff2ae6ddeb907e9c53ed8c45a44d08caa57a260294dd7eabc324bfc1a)
openxpki.service file:
[Unit]
Description=OpenXPKI Trustcenter Backend
After=network.target apache2.service
[Service]
Type=exec
PIDFile=/var/run/openxpkid.pid
ExecStart=/usr/bin/openxpkictl start --nd
ExecStop=/usr/bin/openxpkictl stop
# We want systemd to give the daemon some time to finish gracefully, but
still want
# it to kill httpd after TimeoutStopSec if something went wrong during the
# graceful stop. Normally, Systemd sends SIGTERM signal right after the
# ExecStop, which would kill the daemon. We are sending useless SIGCONT
here to give
# the daemon time to finish.
Restart=on-failure
KillSignal=SIGCONT
PrivateTmp=true
[Install]
WantedBy=multi-user.target
The service runs under the openxpki user:
openxpki 1229 0.3 10.0 116916 95460 ? S Mar27 35:36
openxpkid (main) watchdog (idle)
openxpki 1230 0.0 10.0 117440 95072 ? S Mar27 1:18
openxpkid (main) server
openxpki 1265 0.0 10.8 117460 102260 ? Ss Mar27 1:38
openxpkid (main) server
openxpki 1269 0.3 10.1 116928 95644 ? S Mar27 35:50
openxpkid (main) watchdog (idle)
The OS is Raspian:
root@muffin:/etc/openxpki/webui# cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/";
SUPPORT_URL="http://www.raspbian.org/RaspbianForums";
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs";
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
Windows 10
*From: *Oliver Welter <mailto:m...@oliwel.de>
*Sent: *Friday, April 2, 2021 6:32 AM
*To: *openxpki-users@lists.sourceforge.net
<mailto:openxpki-users@lists.sourceforge.net>
*Subject: *Re: [OpenXPKI-users] FW: Full Certificate Status Report --
drop down menu not populating
The directory is merged by the configuration layer on startup, this is
the stuff in OpenXPKI::Config. The Syntax with the @ Symbol is something
we built into the config layer of OpenXPKI, or to be more precise in the
Connector package which is a stand alone package that we use to read the
config tree. It is like a symlink so item@: report points to the node
report in the reals config which is made from the stuff you find in the
report/ folder structure.
What OS / code packages are you using, how do you start OpenXPKI? In
case you do not start it as root, I suggest you check the permissions
of the report directory and its files - as it shows up when you run
lintconfig as root it might be the problem that you start with a
non-root users that can not read this file.
Oliver
Am 02.04.21 um 08:14 schrieb Mitch Mitchell:
Where in the perl code does it scan that directory. I turned
logging up to debug and still don't see anything unusual. It's
like it looks and finds no files so that's not a failure.
BTW what does item@: mean - I could only find two uses of that
construct and the yaml standard said @ was reserved for future use.
Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------
From: Oliver Welter <m...@oliwel.de> <mailto:m...@oliwel.de>
Date: 3/27/21 10:57 AM (GMT-06:00)
To: Mitch Mitchell <mitchmitchell1...@gmail.com>
<mailto:mitchmitchell1...@gmail.com>
Subject: Re: [OpenXPKI-users] Full Certificate Status Report -- drop
down menu not populating
Am 27.03.21 um 03:26 schrieb Mitch Mitchell:
{
"options": [],
"label": "Report Configuration",
"type": "select",
"name": "report_config"
},
yes and ths is the problem - there are no options.
Are you running an old version of OpenXPKI?
--
Protect your environment - close windows and adopt a penguin!
_______________________________________________
OpenXPKI-users mailing list
OpenXPKI-users@lists.sourceforge.net
<mailto:OpenXPKI-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/openxpki-users
<https://lists.sourceforge.net/lists/listinfo/openxpki-users>
--
Protect your environment - close windows and adopt a penguin!
_______________________________________________
OpenXPKI-users mailing list
OpenXPKI-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openxpki-users
--
Protect your environment - close windows and adopt a penguin!
_______________________________________________
OpenXPKI-users mailing list
OpenXPKI-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openxpki-users
