[ 
https://issues.apache.org/jira/browse/APEXCORE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057870#comment-16057870
 ] 

Pramod Immaneni commented on APEXCORE-712:
------------------------------------------

I think you mean to have SSL_CONFIG as a more complex object like a POJO 
instead of a filename that refers to a file that contains all ssl related 
properties. That works for me in terms of more direct way to specifying these 
properties. Why would we need the long naming, using hadoop specific names, for 
the properties of that object. Why can't they be specified with regular field 
names like keystoreLocation, keystorePassord, keyPassword etc. This way the 
user does not need to be aware of the actual property names being used by 
hadoop and is more portable in case we support another runtime in the future. 
For convenience, for the user, the entire object with the field values can be 
specified as a single String property as defined by the 
StringCodec.Object2String class. I would prefer a more targeted name like 
MANAGEMENT_SSL_CONFIG as I am not sure if this would be enough to support any 
SSL configuration needed in future (like if this is used for encryption data 
flow itself). But, if you want to go with SSL_CONFIG I would be ok.

> Support distribution of custom SSL material to the Stram node while launch 
> the app
> ----------------------------------------------------------------------------------
>
>                 Key: APEXCORE-712
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-712
>             Project: Apache Apex Core
>          Issue Type: Improvement
>            Reporter: Sanjay M Pujare
>            Assignee: devendra tagare
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> This JIRA is dependent on APEXCORE-711. APEXCORE-711 talks about using a 
> custom SSL configuration but assumes the SSL files (ssl-server.xml and the 
> keystore) are already available on any cluster node so when the Stram starts 
> it is able to find them. There are cases where users don't want to do this 
> and they expect the Apex client to package these files so that they are 
> copied to the App master node so when Stram starts it will find them in the 
> expected location.
> Enhance the Apex client/launcher to distribute the custom SSL files (XML and 
> the keystore) along with the application jars/resources so the user does not 
> need to pre-distribute the custom SSL files.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to