Issue #4506
closedssl_client_* and ssl_ca_certificate remote options are difficult to use
Description
The three options:
ssl_ca_certificate
ssl_client_certificate
ssl_client_key
take pem encoded certs, which is base64 encoded, however when i use the bindings to pass them in, pulp throws an error:
{"ssl_ca_certificate":["The submitted data was not a file. Check the encoding type on the
form."],"ssl_client_certificate":["The submitted data was not a file. Check the encoding type on the
form."],"ssl_client_key":["The submitted data was not a file. Check the encoding type on the form."]}
this seem to indicate that they need to be uploaded as a multi-part form (as files)? I'd expect the bindings to handle this if it were the case, but i'm not really sure it'd need to be the case?
In addition, these options are not documented in the remote_file_file_create api, even though the api seems to try to accept them.
Related issues
Problem: ssl fields on remote are hard to use
Solution: switch all ssl fields to TextField
This patch switches the storage of SSL certs, keys, and CAs from filesystem to database. This patch also introduces a new serializer field that returns a SHA256 digest for GET operations.
Required PR: https://github.com/pulp/pulpcore-plugin/pull/91
fixes: #4506 https://pulp.plan.io/issues/4506
re: #4676 https://pulp.plan.io/issues/4676