# Querying the cluster incorrectly, returns the path of the cert in error
**URL:** https://discuss.elastic.co/t/querying-the-cluster-incorrectly-returns-the-path-of-the-cert-in-error/128592
**Category:** Elasticsearch
**Created:** [April 18, 2018, 7:16pm UTC](https://discuss.elastic.co/t/querying-the-cluster-incorrectly-returns-the-path-of-the-cert-in-error/128592 "2018-04-18T19:16:57Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Diadems](https://discuss.elastic.co/u/Diadems)
#### Post date: [April 18, 2018, 7:16pm UTC](https://discuss.elastic.co/t/querying-the-cluster-incorrectly-returns-the-path-of-the-cert-in-error/128592/1 "2018-04-18T19:16:57Z")
> > Is this a bug to be addressed or
> > is it supposed to behave this way?
I tried querying the Elasticsearch cluster with an xpack query like below:
```auto
GET http://elastic-cluster-ip:port/_xpack/ssl/certificates
```
It returned the error as:
```auto
{
"error": {
"root_cause": [
{
"type": "no_such_file_exception",
"reason": "/etc/elasticsearch/certs/ca.p12"
}
],
"type": "no_such_file_exception",
"reason": "/etc/elasticsearch/certs/ca.p12"
},
"status": 500
}
```
Does this also means that if someone is able to crack the user credentials or gets access to it without access to cluster backend, can know details about some if not all cluster configurations?
I am thinking this will also depend on the amount of permissions the user has with which the query was run?
---
### Author:  [@ikakavas](https://discuss.elastic.co/u/ikakavas)
#### Post date: [April 19, 2018, 6:59am UTC](https://discuss.elastic.co/t/querying-the-cluster-incorrectly-returns-the-path-of-the-cert-in-error/128592/2 "2018-04-19T06:59:03Z")
Hi,
This is intended behavior and the API endpoint is documented [here](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/security-api-ssl.html). The fact that you get an error there means that your SSL configuration in `elasticsearch.yml` is not valid. (which doesn't cause an issue now since you clearly have TLS in the http layer off ).
> [@Diadems](#):
>
> Does this also means that if someone is able to crack the user credentials or gets access to it without access to cluster backend, can know details about some if not all cluster configurations?
What would you mean with
> gets access to it without access to cluster backend
exactly ?
The Cluster APIs are detailed [here](https://www.elastic.co/guide/en/elasticsearch/reference/6.2/cluster.html) and yes, as this is their intended purpose, these API endpoints will provide cluster information. I'm not sure I understand your concerns though, as with all systems, when you get access (maliciously or legitimately) to a user account, you can do whatever that user account has the permissions to do .
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 17, 2018, 7:04am UTC](https://discuss.elastic.co/t/querying-the-cluster-incorrectly-returns-the-path-of-the-cert-in-error/128592/3 "2018-05-17T07:04:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.