Project

Profile

Help

Maintenance. Planio will be undergoing a scheduled maintenance this weekend. Between Saturday, July 24 at 9:00 UTC and Sunday, July 25, 22:00 UTC your account might observe occasional downtimes which may last up to several minutes in some cases.

Story #6847

Story #6331: [Epic] Add SSL support

As an installer user, I can configure Pulp to run with TLS enabled using self-signed certificates

Added by bmbouter about 1 year ago. Updated 9 months ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Category:
Installer
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

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

Description

Background

In some cases users of Pulp users want TLS and would like to have self-signed certificates. The motivation is for installations where the user doesn't have existing certs and letsencrypt certs are not an option because the the pulp host is not internet accessible.

Solution

Add options to the installer for the user to express their intent to have Pulp create and use self-signed TLS certificates. If provided, the installer should create self-signed certificates for the hostname of the host. The certificates should be used to configure either the Apache or Nginx configuration Pulp to run on port 443 with TLS enabled.

This option would not be enabled by default.

Associated revisions

Revision 83e9b685 View on GitHub
Added by spredzy 12 months ago

pulp_webserver: Add support for TLS configuration

Enable HTTPS by default when deploying a new pulp server. One can either specify the value of the certificate and the key. Or, if none available, can have the installer generating them.

Support has been added for both nginx and apache.

fixes #6845 https://pulp.plan.io/issues/6845 fixes #6847 https://pulp.plan.io/issues/6847

Co-Authored-By: Matthias Dellweg

Revision 83e9b685 View on GitHub
Added by spredzy 12 months ago

pulp_webserver: Add support for TLS configuration

Enable HTTPS by default when deploying a new pulp server. One can either specify the value of the certificate and the key. Or, if none available, can have the installer generating them.

Support has been added for both nginx and apache.

fixes #6845 https://pulp.plan.io/issues/6845 fixes #6847 https://pulp.plan.io/issues/6847

Co-Authored-By: Matthias Dellweg

History

#1 Updated by bmbouter about 1 year ago

  • Parent task set to #6331

#2 Updated by bmbouter about 1 year ago

  • Tracker changed from Issue to Story
  • % Done set to 0

#3 Updated by pulpbot about 1 year ago

  • Status changed from NEW to POST

#4 Updated by dkliban@redhat.com about 1 year ago

  • Groomed changed from No to Yes
  • Sprint set to Sprint 74

#5 Updated by rchan about 1 year ago

  • Sprint changed from Sprint 74 to Sprint 75

#6 Updated by rchan about 1 year ago

  • Sprint changed from Sprint 75 to Sprint 76

#8 Updated by rchan about 1 year ago

  • Sprint changed from Sprint 76 to Sprint 77

#9 Updated by rchan 12 months ago

  • Sprint changed from Sprint 77 to Sprint 78

#10 Updated by spredzy 12 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#11 Updated by ttereshc 9 months ago

  • Sprint/Milestone set to 3.8.0

#12 Updated by ttereshc 9 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF