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

ASF subversion and git services commented on NIFI-5148:
-------------------------------------------------------

Commit f69b720464d540c8ea32f7ddbc58d08cb566a630 in nifi's branch 
refs/heads/master from [~bbende]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=f69b720 ]

NIFI-5148 Refactoring Kerberos auth for Solr processors
- Created resuable KeytabUser and KeytabConfiguration in nifi-security-utils
- Refactored Solr processors to use a KeytabControllerService and no longer 
rely on JAAS system property
- Wrapped all calls in SolrProcessor onTrigger in a doAs when kerberos is 
enabled
- Added IT tests against MiniKDC
- This closes #2674


> Solr processors failing to authenticate against Kerberized Solr
> ---------------------------------------------------------------
>
>                 Key: NIFI-5148
>                 URL: https://issues.apache.org/jira/browse/NIFI-5148
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>            Reporter: Bryan Bende
>            Assignee: Bryan Bende
>            Priority: Major
>             Fix For: 1.7.0
>
>
> It appears that with the new default value of "useSubjectCredsOnly=true" in 
> NiFi's bootstrap.conf that this can cause an issue for the Solr processors 
> when talking to a kerberized Solr.
> The SolrJ client code that we are using specifically calls this out as being 
> problematic:
> [https://github.com/apache/lucene-solr/blob/branch_6x/solr/solrj/src/java/org/apache/solr/client/solrj/impl/Krb5HttpClientConfigurer.java#L75-L88]
> We should refactor the kerberos approach in the Solr processors to resolve 
> this issue and make general improvements. We should be performing a JAAS 
> login and wrapping calls in Subject.doAs, and we should try and move away 
> from the system level JAAS property and leverage the new keytab controller 
> service.
>  



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

Reply via email to