# After upgrading macos to 14.x, the ElasticEndpoint authorization is automatically closed by the FDA

**URL:** <https://discuss.elastic.co/t/after-upgrading-macos-to-14-x-the-elasticendpoint-authorization-is-automatically-closed-by-the-fda/349328>\
**Category:** Elastic Security\
**Created:** [December 14, 2023, 7:14am UTC](https://discuss.elastic.co/t/after-upgrading-macos-to-14-x-the-elasticendpoint-authorization-is-automatically-closed-by-the-fda/349328 "2023-12-14T07:14:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![xqaiviwjxzw](https://avatars.discourse-cdn.com/v4/letter/x/bbce88/32.png) [@xqaiviwjxzw](https://discuss.elastic.co/u/xqaiviwjxzw)\
**Post date:** [December 14, 2023, 7:14am UTC](https://discuss.elastic.co/t/after-upgrading-macos-to-14-x-the-elasticendpoint-authorization-is-automatically-closed-by-the-fda/349328/1 "2023-12-14T07:14:32Z")

</div>

After installing elastic agent version 8.4.1 and 8.9.1, I have clicked and checked in FDA to authorize ElasticEndpoint. However, after running on the computer for a period of time, the macos version is upgraded to 14.0, 14.1, 14.2, etc., and the authorization of ElasticEndpoint will be automatically closed. Elastic agent is deployed independently and is not deployed using mdm.What is the reason for this?

Is there any way to avoid this?

 ![20231025-132156](https://us1.discourse-cdn.com/elastic/original/3X/d/3/d3d6c5627faa6d80c42029e289ada74e9e82fbb2.jpeg)

---

<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:** [January 11, 2024, 7:14am UTC](https://discuss.elastic.co/t/after-upgrading-macos-to-14-x-the-elasticendpoint-authorization-is-automatically-closed-by-the-fda/349328/2 "2024-01-11T07:14:38Z")

</div>

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