Project

Profile

Help

Issue #3257

closed

pulp does not ask, provide or configure entitlement certificate key

Added by balonik over 6 years ago. Updated almost 4 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
2.14.0
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Hi,

#1 There is no option during 'pulp-admin rpm repo create' to also provide entitlement certificate key
#2 no entitlement certificate key is provided to consumer during binding
#3 pulp-consumer 'rpm bind --repo-id=foo' does not configure any 'sslclientkey' in pulp.repo

Environment:
RHEL 7.4
pulp-consumer-client-2.14.3-1.el7.noarch
pulp-server-2.14.3-1.el7.noarch

Expected Result:
#1 'pulp-admin rpm repo create' should have new option to include entitlement key
#2 during 'pulp-consumer rpm bind' the key should be copied to consumer with certificate
#3 'sslclientkey' should be set in 'pulp.conf' for repository so the 'yum' commands won't fail each time with curl's error 'invalid key'

Thanks.

Actions #1

Updated by jortel@redhat.com over 6 years ago

As a workaround, suggest you include the key (PEM) in the certificate file. YUM should work with that. Can you try that?

Actions #2

Updated by dalley over 6 years ago

  • Triaged changed from No to Yes
Actions #3

Updated by bmbouter about 5 years ago

  • Status changed from NEW to CLOSED - WONTFIX

Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.

Actions #4

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF