Project

Profile

Help

Task #6810

closed

Add a test to ensure FileRemote with client_cert and client_key configured can sync from a protected repository

Added by bmbouter over 2 years ago. Updated 11 months ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulp-certguard/141":https://github.com/pulp/pulp-certguard/issues/141


It's possible to have a Pulp Remote, e.g. FileRemote sync from a CertGaurd protected repo. This should work with either RHSM or X509 Certificate as long as the header is right.

We need to add a test that does the following:

Setup parts of the test

  1. Create a FileRepository and sync some content into it
  2. Create a Publication from (1) and serve it at a FileDistribution

Test sync when it's unprotected

  1. Create a FileRemote and a second repository and sync the FileDistribution from (2) with it

Test sync fails against protected repo without cert_key and client_key

  1. Protect this content with an X509 certificate
  2. Try to sync the second repo using the FileRemote and assert that it fails with a 403 error (because the FileRemote has no client_cert and client_key)

Test sync works when FileRemote has client_cert and client_key

  1. Add the client_cert and client_key to the FileRemote from (3)
  2. Sync the second repo once more and assert it passes
Actions #1

Updated by pulpbot 11 months ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF