[
https://issues.apache.org/jira/browse/SLIDER-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191059#comment-14191059
]
Jonathan Maron commented on SLIDER-263:
---------------------------------------
It turns out that persisting the password to a file does prove useful for
testing (it allows the use of the generated file to be leveraged as keystore by
the AM and truststore by a test client). Therefore, the approach taken is that
the AM does not persist the password. However, if a password file is found it
will use it to read the password. That way a test client can generate a
keystore and associated password that will be utilized by both the AM and the
test client. But this will really only work in a situation where the test
client and AM are running on the same host (unit test).
> AM should not persist keystore password
> ---------------------------------------
>
> Key: SLIDER-263
> URL: https://issues.apache.org/jira/browse/SLIDER-263
> Project: Slider
> Issue Type: Bug
> Reporter: Jonathan Maron
> Assignee: Jonathan Maron
> Fix For: Slider 0.60
>
>
> Much like the accumulo approach in SLIDER-254, look at using the credential
> provider in the context of establishing SSL communication between the App
> Master and agents in spawned containers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
