# Service Licensing: setting permissions to read access to configuration files

**URL:** <https://discuss.elastic.co/t/service-licensing-setting-permissions-to-read-access-to-configuration-files/141356>\
**Category:** Logstash\
**Created:** [July 24, 2018, 10:36am UTC](https://discuss.elastic.co/t/service-licensing-setting-permissions-to-read-access-to-configuration-files/141356 "2018-07-24T10:36:26Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![msaboor35](https://avatars.discourse-cdn.com/v4/letter/m/e47c2d/32.png) [@msaboor35](https://discuss.elastic.co/u/msaboor35)\
**Post date:** [July 24, 2018, 10:36am UTC](https://discuss.elastic.co/t/service-licensing-setting-permissions-to-read-access-to-configuration-files/141356/1 "2018-07-24T10:36:26Z")

</div>

0  
down vote  
favorite

I am making a software solution using ELK stack. I am setting up a demo for a company but I don't want them to steal my configuration files of elasticsearch, logstash, kibana, filebeat, e.t.c. I am setting the demo on their server but have no clue how to stop them reading/copying the configuration files.

P.S can someone suggest a way to set it up for a trial period. My idea is to stop the services using cron job and then delete the configuration files.

I would be happy to hear any other suggestions related to licensing scheme of this type of service.

---

<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:** [August 21, 2018, 10:36am UTC](https://discuss.elastic.co/t/service-licensing-setting-permissions-to-read-access-to-configuration-files/141356/2 "2018-08-21T10:36:41Z")

</div>

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