Actions
Issue #4891
closedThe client side ssl cert for pulp should follow http header standards
Start date:
Due date:
Estimated time:
Severity:
1. Low
Platform Release:
OS:
Triaged:
Yes
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 68
Quarter:
Description
The client side cert is currently coming in via SSL_CLIENT_CERTIFICATE
It should probably be change to conform to the X-header standards and be X-SSL_CLIENT_CERTIFICATE
The is for the certguard plugin for pulp3.
Updated by bmbouter over 5 years ago
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
we should fix this, I'm grooming so it can go on the sprint.
Updated by bmbouter over 5 years ago
- Sprint set to Sprint 54
These weren't added to Sprint 54, but they were OK'd at sprint planning.
Updated by dkliban@redhat.com over 5 years ago
- Sprint changed from Sprint 55 to Sprint 56
Updated by bmbouter almost 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
- Sprint Candidate set to No
- Sprint set to Sprint 68
Moving onto sprint as this backwards incompatible change should be done for the GA release of pulp-certguard.
Updated by bmbouter almost 5 years ago
- Status changed from ASSIGNED to POST
PR available at: https://github.com/pulp/pulp-certguard/pull/46
Added by bmbouter almost 5 years ago
Updated by bmbouter almost 5 years ago
- Status changed from POST to MODIFIED
Applied in changeset 1a0c02e1d96fa2a292248c81f9812119923e4c9d.
Updated by bmbouter over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Rename SSL-CLIENT-CERTIFICATE to X-CLIENT-CERT
This adds a backwards incompatible release note along with updates to the code, tests, and docs.
https://pulp.plan.io/issues/4891 closes #4891