As a user I have path checking features for to the X.509 certguard
Ticket moved to GitHub: "pulp/pulp-certguard/138":https://github.com/pulp/pulp-certguard/issues/138
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.
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 dustball about 2 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.