# Config flag DoNotForceCN

**URL:** <https://community.letsencrypt.org/t/config-flag-donotforcecn/20827>\
**Category:** Feature Requests\
**Created:** [October 8, 2016, 8:27pm UTC](https://community.letsencrypt.org/t/config-flag-donotforcecn/20827 "2016-10-08T20:27:05Z")\
**Posts on this page:** 2\
**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:** [October 8, 2016, 8:27pm UTC](https://community.letsencrypt.org/t/config-flag-donotforcecn/20827/1 "2016-10-08T20:27:05Z")

</div>

From what I understand (see [Empty CommonName in CSR](https://community.letsencrypt.org/t/empty-commonname-in-csr/14344)), what’s needed to enable the DoNotForceCN flag is some work on CP documents.  
Cannot these modifications and legal audits be done together with the IDN support (see [https://github.com/letsencrypt/boulder/issues/597#issuecomment-252036300](https://github.com/letsencrypt/boulder/issues/597#issuecomment-252036300))?

---

<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:** [November 7, 2016, 8:31pm UTC](https://community.letsencrypt.org/t/config-flag-donotforcecn/20827/2 "2016-11-07T20:31:19Z")

</div>

Closed on November 7, 2016, 8:31pm UTC

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