Actions
Story #6324
closedCertGuard - Task #6323: [Epic] Move certguard authentication from pulp-content to apache and nginx access scripts
As a user, CertGuard checking does *not* happen in pulp-content
Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 68
Quarter:
Description
As part of Epic 6323 we need to have content guard checking removed from the pulp-content app and have the reverse proxy or webserver in front of pulp-content perform the authorization check.
This ticket is specifically for removing the CertGuard checking from pulp-content.
Updated by bmbouter about 4 years ago
- Parent issue set to #6323
- Sprint set to Sprint 7
Updated by dkliban@redhat.com about 4 years ago
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
- Sprint changed from Sprint 7 to Sprint 68
Updated by bmbouter about 4 years ago
- Status changed from NEW to CLOSED - WONTFIX
We are keeping authorization in the Pulp services and not in the webserver themselves. The summary of reasons is here: https://www.redhat.com/archives/pulp-dev/2020-March/msg00035.html As such this story should be closed.
Actions