Story #4666
closed
As a user I have path checking features for to the X.509 certguard
0%
Description
Ticket moved to GitHub: "pulp/pulp-certguard/138":https://github.com/pulp/pulp-certguard/issues/138
Motivation¶
It would be very useful for paths to be put into the x.509 extended attributes to see if this client is authorized to access this specific distribution's content. This way whoever is generating the certs (and their expiration dates) determines the access.
Solution¶
The existing X.509 certguard could automatically be updated to check this correctly. We also need docs with how the openssl tooling can easily make these kind of certs.
How will we ensure path checking is required?¶
A boolean will be added to the X.509 certguard called path_check_required which will default to False. If True, the certificate check must contain a matching path for the content requested.
Updated by bmbouter over 4 years ago
- Description updated (diff)
revising with details about how users can configure that path checking is required
Updated by bmbouter over 4 years ago
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
We should add this to the sprint.
Updated by bmbouter over 4 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 4 years ago
- Sprint changed from Sprint 55 to Sprint 56
Updated by rchan about 4 years ago
Not moving forward to next Sprint to make room for highest priority Katello blockers.
Updated by dustball about 3 years ago
I'm interested in this feature as well, we're serving a large amount of customers with all different kinds of systems.
We want to offer our customers staging for licensed products via a central pulpserver as well and individually allow or deny access to those repositories.
Updated by pulpbot almost 2 years ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
.