[ 
https://issues.apache.org/jira/browse/SOLR-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mano Kovacs updated SOLR-10307:
-------------------------------
    Attachment: SOLR-10307.patch

Thank you for the review, [[email protected]]. Uploading second patch.

bq. Only suggestion I have is that it might be nice to add a sentence comment 
to Configurations init and setupSSLStorePasswords so that you can quickly tell 
what these methods do and how they should be called.

I added brief documentation for {{init}} and {{setupSSLStorePasswords}}. 

bq. Might use something less generic than Configurations as well, even if it's 
EnvVarConfigurations or something.

I was planning to add further configuration options to this class later 
(probably something with Hadoop Credential Provider Interface), which would 
suggest a more generic name. If you agree, I would use a more generic name.

> Provide SSL/TLS keystore password a more secure way
> ---------------------------------------------------
>
>                 Key: SOLR-10307
>                 URL: https://issues.apache.org/jira/browse/SOLR-10307
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: security
>            Reporter: Mano Kovacs
>            Assignee: Mark Miller
>         Attachments: SOLR-10307.patch, SOLR-10307.patch
>
>
> Currently the only way to pass server and client side SSL keytstore and 
> truststore passwords is to set specific environment variables that will be 
> passed as system properties, through command line parameter.
> First option is to pass passwords through environment variables which gives a 
> better level of protection. Second option would be to use hadoop credential 
> provider interface to access credential store.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to