# Enrollent Token. Can we totally set to false permanently?

**URL:** <https://discuss.elastic.co/t/enrollent-token-can-we-totally-set-to-false-permanently/357686>\
**Category:** Elastic Security\
**Created:** [April 18, 2024, 9:27am UTC](https://discuss.elastic.co/t/enrollent-token-can-we-totally-set-to-false-permanently/357686 "2024-04-18T09:27:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Beyond\_Sky](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/beyond_sky/32/128633_2.png) [@Beyond\_Sky](https://discuss.elastic.co/u/Beyond_Sky)\
**Post date:** [April 18, 2024, 9:27am UTC](https://discuss.elastic.co/t/enrollent-token-can-we-totally-set-to-false-permanently/357686/1 "2024-04-18T09:27:07Z")

</div>

Basically adding a new elasticsearch nodes, it require the adding of enrollment token and it is checked by ip address. Our certificates provided hostname but elasticsearch checks ip only. Is there a way to use hostname instead?

This was the response when create enrollment token:  
_No subject alternative names matching IP address xxx_ ._xxx_ ._xxx_ ._xxx found_ .

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 16, 2024, 9:27am UTC](https://discuss.elastic.co/t/enrollent-token-can-we-totally-set-to-false-permanently/357686/2 "2024-05-16T09:27:10Z")

</div>

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