New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove "Request Certificate with SubjectAltName" permission #299
Remove "Request Certificate with SubjectAltName" permission #299
Conversation
|
I have put on my Travis moustache and found these two failing tests, you will have to fix them: I also wonder if there is a possibility for this removal to break replica install against older (IPA v3) masters. |
|
Bumping this PR as it seems a bit forgotten. |
|
On Tue, Dec 20, 2016 at 07:11:08AM -0800, Martin Babinsky wrote:
Bumping this PR as it seems a bit forgotten.
Cheers. Not forgotten, just not my top priority right now.
|
subjectAltName is required or relevant in most certificate use cases (esp. TLS, where carrying DNS name in Subject DN CN attribute is deprecated). Therefore it does not really make sense to have a special permission for this, over and above "request certificate" permission. Furthermore, we already do rigorously validate SAN contents again the subject principal, and the permission is waived for self-service requests or if the operator is a host principal. So remove the permission, the associated virtual operation, and the associated code in cert_request. Fixes: https://fedorahosted.org/freeipa/ticket/6526
524e1ab
to
837a225
Compare
|
@martbab I don't think this will break migrations from v3; it does not actively remove the permission from existing deployments, it just doesn't add it for new installations. (Admittedly, it is the next thing to test but I have not done so yet). |
|
Fixed upstream |
Fixes: https://fedorahosted.org/freeipa/ticket/6526
Note: the ticket hasn't been triaged or even agreed to. But here is the code
^_^
subjectAltName is required or relevant in most certificate use cases
(esp. TLS, where carrying DNS name in Subject DN CN attribute is
deprecated). Therefore it does not really make sense to have a
special permission for this, over and above "request certificate"
permission.
Furthermore, we already do rigorously validate SAN contents again
the subject principal, and the permission is waived for self-service
requests or if the operator is a host principal.
So remove the permission, the associated virtual operation, and the
associated code in cert_request.