-
Notifications
You must be signed in to change notification settings - Fork 27
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
Generate CSR at runtime #30
Comments
Hello Simkiw, We already support generating the CSR in another command, Regards, |
@toddgaunt-gs - The request for client generation of CSR at run-time based upon tls-unique (TLSv1.2) or tls-exporter (TLSv1.3) is in line with RFC 7030 requirements for linking identity and client proof-of-possession of the CSR private key. See Section 3.5 of RFC 7030 for details. While not mandatory, this functionality is highly useful to ensure the authenticity of the EST request. |
Exactly @61131 @toddgaunt-gs , I actually looked at the client implementation too. |
Thanks for the clarification both of you. This would be useful feature to implement indeed. Since this is meant as an example EST service and we don't use this functionality in our own environment this likely won't be prioritized for implementation, however I'd be happy to accept a PR implementing this functionality and to get another developer and myself to review it. |
Sure, |
Hello,
The package implements different APIs of EST protocol.
It expects the CSR to be ready for use, like in the enroll method.
Is it possible to generate the CSR at runtime?
And can we fetch the TLS unique value from the current client implementation?
Typical use-case: include TLS-unique value (in TLS 1.2)
Such as, after establishing the TLS connection between server and client,
Thank you very much
The text was updated successfully, but these errors were encountered: