Project

Profile

Help

Issue #4506

closed

ssl_client_* and ssl_ca_certificate remote options are difficult to use

Added by jsherril@redhat.com over 5 years ago. Updated over 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Category:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Sprint 52
Quarter:

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

Related to Pulp - Task #2455: Store SSL certificates on the filesystem instead of DBCLOSED - CURRENTRELEASEjortel@redhat.com

Actions
Related to Pulp - Test #5270: Test - Syncing with ssl client certs and ca certCLOSED - DUPLICATEActions
Related to File Support - Issue #5352: Unable to sync using SSL certs from distribution with cert-guardsCLOSED - DUPLICATEActions

Also available in: Atom PDF