Hello Antonio,
there is one pitfall that has not been fixed in the community workflow
yet :(
The name of the endpoint is derived from the URL path and used to find
the configuration file. Due to the nature of the configuration tree of
OpenXPKI, no error is triggered when this configuration file is not
found and the result is that the workflow is started without any
configuration items which is then caught by the profile check. Long
story short - make sure you have a the endpoint configured properly,
details are here
https://openxpki.readthedocs.io/en/latest/subsystems/index.html#wrapper-configuration
Oliver
On 13.07.23 18:05, Antonio Gamboa wrote:
Hi Martin.
Thanks for your response.
I think the certificate profile 'tls_server' is OK (I have the profile
in the profiles' directory) even, I can see it and use it on the web UI.
I tried specifying the certificate profile in the RPC request
(tls-server, due to the mapping) but the message is the same.
What happens if the CSR not has the required subject data? The message
is different from "Invalid Profile"
Cheers.
Gamboa
_______________________________________________
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
