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

Support for the E (email) tag #826

Closed
Narev opened this issue Nov 22, 2017 · 4 comments · Fixed by #1172
Closed

Support for the E (email) tag #826

Narev opened this issue Nov 22, 2017 · 4 comments · Fixed by #1172

Comments

@Narev
Copy link

Narev commented Nov 22, 2017

It seems that when you generate a certifcate with an E tag/attribute in the csr it is omitted. The same goes for if you generate your own csr that contains an E tag the generated certificate will not copy the email tag. Would it be possible to include this tag?

@ghost
Copy link

ghost commented Aug 7, 2018

Have you found any workarounds to embed e-mail into the certificate?

@Narev
Copy link
Author

Narev commented Aug 7, 2018 via email

@cubicrace
Copy link

cubicrace commented Feb 5, 2021

Do we have a date on when this could be fixed ? Microsoft / Jamf SCEP profiles allow to add the E attribute to certificate subjects and this could break the feature for a lot of customers

@aklyachkin
Copy link
Contributor

The origin of the problem seems to be here - https://golang.org/pkg/crypto/x509/pkix/#Name
There is no field for e-mail in the standard Go library

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.

3 participants