# Elasticsearch 7.2 on Windows security problem **URL:** \ **Category:** Elasticsearch\ **Created:** [August 1, 2019, 8:56pm UTC](https://discuss.elastic.co/t/elasticsearch-7-2-on-windows-security-problem/193406 "2019-08-01T20:56:43Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![tdmboro](https://avatars.discourse-cdn.com/v4/letter/t/ed8c4c/32.png) [@tdmboro](https://discuss.elastic.co/u/tdmboro)\ **Post date:** [August 1, 2019, 8:56pm UTC](https://discuss.elastic.co/t/elasticsearch-7-2-on-windows-security-problem/193406/1 "2019-08-01T20:56:43Z")
TLDR; it seems the built-in account set is losing credential setup information under certain conditions, maybe due to incorrect config? See config below. Now for story time... I have a basic license, single node installation of elasticsearch, being used as a data repository for a python application. I'm very new to elastic in general so don't assume I know what I'm doing with server config. I managed to configure SSL and turn on authentication, but the built-in accounts (especially "elastic") aren't holding their passwords. In fact, once they "let go", I can set them again using the "bin\elasticsearch-setup-passwords" utility (subsequent attempts to use the utility fail with the usual error until the event recurs). There's no entries in the log when this happens, other than a failed elastic login from me attempting and failing a call to learn that the problem has recurred. It doesn't coincide with an elastic service restart, and there are no errors in the elasticsearch.log other than the auth failures. My guess is that I have done something unexpected with config, or there's something that "should" be obvious to me that I've missed that is somehow causing the basic creds to not persist. What's interesting is that every "loss" of built-in creds seems to coincide with a call from Postman that hangs (never returns, isn't logged, interesting...). I have never seen the behavior when making calls from Python (requests library, not the elastic one). elasticsearch.yml: bootstrap.memory\_lock: true cluster.name: elasticsearch network.host: 0 discovery.seed\_hosts: 127.0.0.1 http.port: 443 node.data: true node.ingest: true node.master: true node.max\_local\_storage\_nodes: 1 node.name: data path.data: C:\ProgramData\Elastic\Elasticsearch\data path.logs: C:\ProgramData\Elastic\Elasticsearch\logs transport.tcp.port: 9300 xpack.license.self\_generated.type: basic xpack.security.enabled: true xpack.security.authc.accept\_default\_password: false xpack.security.transport.ssl.enabled: true xpack.security.transport.ssl.verification\_mode: certificate xpack.security.transport.ssl.keystore.path: certs\azure-fqdn-redacted.p12 xpack.security.transport.ssl.truststore.path: certs\azure-fqdn-redacted.p12 xpack.security.http.ssl.enabled: true xpack.security.http.ssl.keystore.path: certs\azure-fqdn-redacted.p12 xpack.security.http.ssl.truststore.path: certs\azure-fqdn-redacted.p12 ---
**Author:** ![fjohnson88](https://avatars.discourse-cdn.com/v4/letter/f/ecb155/32.png) [@fjohnson88](https://discuss.elastic.co/u/fjohnson88)\ **Post date:** [August 5, 2019, 5:00pm UTC](https://discuss.elastic.co/t/elasticsearch-7-2-on-windows-security-problem/193406/2 "2019-08-05T17:00:58Z")
I am by no means an ES expert, but if I had to guess, something in Postman may be trucking it over your .security index. See: [https://www.elastic.co/guide/en/elastic-stack-overview/current/built-in-users.html](https://www.elastic.co/guide/en/elastic-stack-overview/current/built-in-users.html) Hope that helps! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 2, 2019, 5:01pm UTC](https://discuss.elastic.co/t/elasticsearch-7-2-on-windows-security-problem/193406/3 "2019-09-02T17:01:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.