-
Notifications
You must be signed in to change notification settings - Fork 26
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
certsrv.get_cert with attributes #9
Comments
Hi! No, this is not possible at the moment, but should be an easy fix. Out of curiosity; any reason why you just don't include the SAN in the CSR? I believe it's bad practice to allow SANs to be specified in the request attributes. |
The application that I generate the CSR through does not support adding any SANs. Do I need to open a feature request? |
I see. I fixed this in the v2 branch: 0a06220 I'm planning on releasing v2 in a couple of weeks. |
Cheers! Thank you! |
Is there an ETA for v2? Would love to integrate this into my workflow but need the attribute capability. |
Sorry about the wait, I will release v2 in the coming week. |
I released v2 just now. Sorry it took so long. Hope it works for you! |
@defiant214 Did this work out for you? :-) |
I apologize. I haven't had a chance to try it yet! My project has been on hold for a few months, as more important things sidetracked me. :-( |
No problem, that's life! Just let me know when you get the opportunity to test. |
Is there a way to add additional attributes to the cert request? For example, I frequently include subject alternate name (SAN) fields using the
san:dns=dns.name[&dns=dns.name]
format.The text was updated successfully, but these errors were encountered: