Hi,
> I'm trying to issue a certificate using the default RPC configuration
> (RequestCertificate method) but a get :
> {
> "result": {
> "id": 3583,
> "proc_state": "finished",
> "state": "FAILURE",
> "data": {
> "transaction_id": "723c94cd1fba71e96d1a5c240fdebf9801f74a1d",
> "error_code": "Invalid Profile"
> },
> "pid": 3481
> }
> }
>
> I'm not setting a certificate profile in the request, I guess it's
> determining the certificate profile from my realm configuration
> (config.d/realm/df/rpc/enroll.yaml)
>
> profile:
> cert_profile: tls_server
> cert_subject_style: enroll
>
> # Mapping of names to OpenXPKI profiles to be used with the
> # Microsoft Certificate Template Name Ext. (1.3.6.1.4.1.311.20.2)
> profile_map:
> pc-client: tls_client
> tls-server: tls_server
> tls-client: tls_client
> #renewal-test: renewal_test
>
> But honestly I don't understand the message "Invalid Profile"
The system is telling you that it does not know which profile to use: the error
happens if the enrollment workflow does not have information about the
certificate profile to use.
Make sure that the profile tls_server (the default profile as per the above
configuration) exists or specify an existing profile in the RPC request.
Note that the value you are sending is mapped via profile_map to the actual
profiles in your PKI Realm.
Cheers
Martin
_______________________________________________
OpenXPKI-users mailing list
OpenXPKI-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openxpki-users
