# Custom extendedKeyUsage stripped from CSR while generating cert

**URL:** <https://community.letsencrypt.org/t/custom-extendedkeyusage-stripped-from-csr-while-generating-cert/17759>\
**Category:** Feature Requests\
**Created:** [July 9, 2016, 5:12pm UTC](https://community.letsencrypt.org/t/custom-extendedkeyusage-stripped-from-csr-while-generating-cert/17759 "2016-07-09T17:12:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pfg](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pfg/32/1924_2.png) [@pfg](https://community.letsencrypt.org/u/pfg)\
**Post date:** [July 9, 2016, 6:30pm UTC](https://community.letsencrypt.org/t/custom-extendedkeyusage-stripped-from-csr-while-generating-cert/17759/2 "2016-07-09T18:30:31Z")

</div>

Public CAs typically only allow a small number of EKU flags that are mentioned in the Certification Practice Statement (CPS), in Let’s Encrypt’s case that’s `id-kp-serverAuth` and `id-kp-clientAuth`.

CSRs are more or less a wishlist that gets “rewritten” based on what the CA supports (and is allowed to support).

---

_[View the full topic](https://community.letsencrypt.org/t/custom-extendedkeyusage-stripped-from-csr-while-generating-cert/17759)._
