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

Mark Miller commented on SOLR-10783:
------------------------------------

Tests look good [~manokovacs], but precommit seems to be giving:

{noformat}
validate-source-patterns:
[source-patterns] File uses Mockito but has no assumeWorkingMockito() call: 
solr/core/src/test/org/apache/solr/util/configuration/SSLConfigurationsTest.java
[source-patterns] File uses Mockito but has no assumeWorkingMockito() call: 
solr/core/src/test/org/apache/solr/util/configuration/providers/HadoopSSLCredentialProviderTest.java

BUILD FAILED
/data1/ssd/lucene-solr-workspace/lucene-solr-1/build.xml:128: Found 2 
violations in source files (File uses Mockito but has no assumeWorkingMockito() 
call).
{noformat}

> Using Hadoop Credential Provider as SSL/TLS store password source
> -----------------------------------------------------------------
>
>                 Key: SOLR-10783
>                 URL: https://issues.apache.org/jira/browse/SOLR-10783
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: security
>    Affects Versions: 7.0
>            Reporter: Mano Kovacs
>            Assignee: Mark Miller
>            Priority: Major
>         Attachments: SOLR-10783-fix.patch, SOLR-10783.patch, 
> SOLR-10783.patch, SOLR-10783.patch, SOLR-10783.patch, SOLR-10783.patch, 
> SOLR-10783.patch
>
>
> As a second iteration of SOLR-10307, I propose support of hadoop credential 
> providers as source of SSL store passwords. 
> Motivation: When SOLR is used in hadoop environment, support of  HCP gives 
> better integration and unified method to pass sensitive credentials to SOLR.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to