Am 15.10.20 um 08:45 schrieb Artur Kańczugowski:
> On 15.10.2020 08:12, Oliver Welter wrote:
>> Hi Artur
>>
>>> $openxpkicmd --realm MY_CA crl_issuance
>>> Log4perl: Seems like no initialization happened. Forgot to call init()?
>>> I18N_OPENXPKI_CLIENT_SEND_RECEIVE_SERVICE_MSG_ERROR_DURING_SEND_SERVICE_MSG;
>>>
>>> __EVAL_ERROR__ => I18N_OPENXPKI_CLIENT_INIT_CONNECTION_FAILED;
>>> __ERROR__ => No such file or directory, __SOCKETFILE__ => /var/openxpki
>>
>> Did you truncate this message? The socketfile location is
>> /var/openxpki/openxpki.socket.
>>
>> If this is not the reason then your server did not start - check the
>> stderr.log and openxpki.log.
>
> Right, sorry, it was my oversight - now, when the server is running I
> get:
>
> $openxpkicmd --realm MY_REALM crl_issuance
> Error:
> $VAR1 = {
> 'LIST' => [
> {
> 'LABEL' => 'ACL does not permit call to API
> command',
> 'PARAMS' => {
> '__caller__' =>
> '/usr/share/perl5/OpenXPKI/Service/Default/CommandApi2.pm:77',
> '__command__' =>
> 'create_workflow_instance'
> }
> }
> ],
> 'SERVICE_MSG' => 'ERROR'
> };
>
> To be specific, I do copied my acl section from old enrollment.yaml
> (double checked)
>
The problem relates to the ACL of the API which was reintroduced in 3.0:
https://github.com/openxpki/openxpki-config/blob/community/UPGRADEv3.md#acl
https://github.com/openxpki/openxpki-config/blob/community/config.d/realm.tpl/api/acl.yaml
Oliver
--
Protect your environment - close windows and adopt a penguin!
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users
