# Accessing settings in the keystore
**URL:** https://discuss.elastic.co/t/accessing-settings-in-the-keystore/114763
**Category:** Elasticsearch
**Created:** [January 9, 2018, 10:19pm UTC](https://discuss.elastic.co/t/accessing-settings-in-the-keystore/114763 "2018-01-09T22:19:41Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@Ivan](https://discuss.elastic.co/u/Ivan)
#### Post date: [January 9, 2018, 10:19pm UTC](https://discuss.elastic.co/t/accessing-settings-in-the-keystore/114763/1 "2018-01-09T22:19:41Z")
How can properties be read from the keystore from inside a plugin? The only
current usage in the main repo is the s3 repository, but that code is
complex (in terms of the amount of calls) and I rather not have to debug
it. Simply want to read the value.
I am still on 5.x if that matters.
Cheers,
Ivan
---
### Author:  [@rjernst](https://discuss.elastic.co/u/rjernst)
#### Post date: [January 9, 2018, 10:33pm UTC](https://discuss.elastic.co/t/accessing-settings-in-the-keystore/114763/2 "2018-01-09T22:33:10Z")
Are you wanting to read an existing secure setting, or your own plugins setting? If your own, you need to create a SecureSetting instance, return that from getSettings() on your plugin, and then use that Setting object to read the value of the setting from Settings once your plugin is initialized.
---
### Author:  [@Ivan](https://discuss.elastic.co/u/Ivan)
#### Post date: [January 9, 2018, 11:16pm UTC](https://discuss.elastic.co/t/accessing-settings-in-the-keystore/114763/3 "2018-01-09T23:16:38Z")
I already found out the answer, but since this mailing list does not send
an email to the sender, I could not reply. Not sure if I can reply to my
original sent email or would that create a new thread.
At first I got it working but creating a KeystoreWrapper and then
decrypting it with an empty password, but I thought that surely that method
cannot be correct. Then I found the SecureString class.
There should be a development mailing list for those that like work on the
_cough_undocumented_cough_ internals. 😉
Thanks,
Ivan
---
### Author:  [@Ivan](https://discuss.elastic.co/u/Ivan)
#### Post date: [January 10, 2018, 12:39am UTC](https://discuss.elastic.co/t/accessing-settings-in-the-keystore/114763/4 "2018-01-10T00:39:24Z")
Not sure if this is a bug that has been resolved or not, but the keystore
only saves one of the values. Using version 5.5.3
integTestCluster {
keystoreSetting 'foo', 'abc'
keystoreSetting 'bar', 'xyz'
keystoreSetting 'baz', 'qwerty'
}
public class MyPlugin extends Plugin implements IngestPlugin {
```
static final Setting FOO =
```
SecureSetting.secureString("foo", null);
static final Setting BAR =
SecureSetting.secureString("bar", null);
static final Setting BAZ =
SecureSetting.secureString("baz", null);
```
@Override
public Map
```
getProcessors(Processor.Parameters parameters) {
Logger logger = Loggers.getLogger(getClass());
```
SecureString foo = FOO.get(parameters.env.settings());
SecureString bar = BAR.get(parameters.env.settings());
SecureString baz = BAZ.get(parameters.env.settings());
logger.warn("all settings {}",
```
parameters.env.settings().toDelimitedString('\n'));
logger.warn("foo: {} for {}", foo, FOO.getKey());
logger.warn("bar: {} for {}", bar, BAR.getKey());
logger.warn("baz: {} for {}", bar, BAZ.getKey());
```
return new HashMap<>();
}
@Override
public List> getSettings() {
return Arrays.asList(FOO, BAR, BAZ);
}
```
}
returns
foo: qwerty for foo
bar: qwerty for bar
baz: qwerty for baz
integTestCluster {
keystoreSetting 'foo', '1'
keystoreSetting 'bar', '2'
keystoreSetting 'baz', '3'
}
returns
foo: 3 for foo
bar: 3 for bar
baz: 3 for baz
Hopefully you can comment before I open an issue.
Thanks,
Ivan
---
### Author:  [@Ivan](https://discuss.elastic.co/u/Ivan)
#### Post date: [January 10, 2018, 12:48am UTC](https://discuss.elastic.co/t/accessing-settings-in-the-keystore/114763/5 "2018-01-10T00:48:25Z")
And just to eliminate gradle issues:
project.afterEvaluate {
logger.warn(integTestCluster.keystoreSettings.toString())
}
[bar:2, foo:1, baz:3]
---
### Author:  [@rjernst](https://discuss.elastic.co/u/rjernst)
#### Post date: [January 10, 2018, 12:54am UTC](https://discuss.elastic.co/t/accessing-settings-in-the-keystore/114763/6 "2018-01-10T00:54:43Z")
I believe this was already fixed. Let me find the issue.
---
### Author:  [@rjernst](https://discuss.elastic.co/u/rjernst)
#### Post date: [January 10, 2018, 1:03am UTC](https://discuss.elastic.co/t/accessing-settings-in-the-keystore/114763/7 "2018-01-10T01:03:23Z")
Here you go, fixed in 5.6.0:
>
---
### Author:  [@Ivan](https://discuss.elastic.co/u/Ivan)
#### Post date: [January 10, 2018, 1:18am UTC](https://discuss.elastic.co/t/accessing-settings-in-the-keystore/114763/8 "2018-01-10T01:18:32Z")
Looks like I need to ugprade, at least it is not to 6.x. I looked for
"keystore" issues, so this one escaped me. Although it makes sense, that
bug would have taken me a bit to find!
---
### Author:  [@rjernst](https://discuss.elastic.co/u/rjernst)
#### Post date: [January 10, 2018, 1:36am UTC](https://discuss.elastic.co/t/accessing-settings-in-the-keystore/114763/9 "2018-01-10T01:36:57Z")
Groovy is a horrible drug. 🙂
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 7, 2018, 1:37am UTC](https://discuss.elastic.co/t/accessing-settings-in-the-keystore/114763/10 "2018-02-07T01:37:20Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.