# Empty CommonName in CSR

**URL:** <https://community.letsencrypt.org/t/empty-commonname-in-csr/14344>\
**Category:** Feature Requests\
**Created:** [April 15, 2016, 4:15am UTC](https://community.letsencrypt.org/t/empty-commonname-in-csr/14344 "2016-04-15T04:15:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![yaslama](https://avatars.discourse-cdn.com/v4/letter/y/ec9cab/32.png) [@yaslama](https://community.letsencrypt.org/u/yaslama)\
**Post date:** [April 15, 2016, 4:15am UTC](https://community.letsencrypt.org/t/empty-commonname-in-csr/14344/1 "2016-04-15T04:15:43Z")

</div>

Do you know when the config flag DoNotForceCN will be set to true, so one can use a CSR with an empty common name ?  
I need to create a certificate with SAN entries longer than 64 characters and the certificate is created in staging but not in production. The error I receive is “urn:acme:error:malformed - Error creating new cert :: Common name was longer than 64 bytes, was 0” because the line [https://github.com/letsencrypt/boulder/blob/25b45a45eca7522bf623a9994cbccdf366adf3b9/ca/certificate-authority.go#L442](https://github.com/letsencrypt/boulder/blob/25b45a45eca7522bf623a9994cbccdf366adf3b9/ca/certificate-authority.go#L442) in executed and not the line [https://github.com/letsencrypt/boulder/blob/25b45a45eca7522bf623a9994cbccdf366adf3b9/ca/certificate-authority.go#L537](https://github.com/letsencrypt/boulder/blob/25b45a45eca7522bf623a9994cbccdf366adf3b9/ca/certificate-authority.go#L537)  
Thanks a lot for the hard work.

Edit: In summary, I am asking when the feature described in [Certificates with serialNumber in subject](https://community.letsencrypt.org/t/certificates-with-serialnumber-in-subject/11891) will be deployed in production.

---

<div class="post-metadata">

**Author:** ![jsha](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jsha/32/12_2.png) [@jsha](https://community.letsencrypt.org/u/jsha)\
**Post date:** [April 15, 2016, 4:27am UTC](https://community.letsencrypt.org/t/empty-commonname-in-csr/14344/2 "2016-04-15T04:27:45Z")

</div>

We don’t yet have an ETA, I’m sorry. We discovered that we need an updated to our CP, one of the [documents](https://letsencrypt.org/repository/) that describes our operations. That’s still pending. Ballpark, maybe in the next month or so. Hearing from folks like you that need the feature enabled does help prioritize it, thanks!

---

<div class="post-metadata">

**Author:** ![yaslama](https://avatars.discourse-cdn.com/v4/letter/y/ec9cab/32.png) [@yaslama](https://community.letsencrypt.org/u/yaslama)\
**Post date:** [April 15, 2016, 4:46am UTC](https://community.letsencrypt.org/t/empty-commonname-in-csr/14344/3 "2016-04-15T04:46:45Z")

</div>

Thanks a lot for your answer. Even a ballpark ETA can help me to decide if I want to use a workaround.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [May 15, 2016, 4:47am UTC](https://community.letsencrypt.org/t/empty-commonname-in-csr/14344/4 "2016-05-15T04:47:02Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.