Skip to content
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

X509v3 extensions from certificate not transferred to CSR #122

Open
nicopal opened this issue May 30, 2023 · 1 comment
Open

X509v3 extensions from certificate not transferred to CSR #122

nicopal opened this issue May 30, 2023 · 1 comment

Comments

@nicopal
Copy link

nicopal commented May 30, 2023

Hi,

After creating a certificate with several X509v3 extensions (e.g. X509v3 Extended Key Usage: TLS Web Client Authentication), I create a certificate signing request using e.g.
certificate.serialize_request_der()

However, the certificate signing request does not contain the extensions. This is in line with an earlier issue in OpenSSL, where extensions from the certificate were not transferred to the CSR and vice versa. This appears to have been fixed by now: openssl/openssl#10458

Do you plan to add a feature to copy X509v3 extensions from the certificate into the CSR?

Thanks.

@cpu
Copy link
Member

cpu commented May 17, 2024

EKU params are being passed into CSRs as of #264

We can leave this open for a more general solution but I thought it would be helpful for you to know this since extended key usages was the usecase mentioned in the original issue text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants