You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Houston Putman (Jira)" <ji...@apache.org> on 2020/08/19 21:26:02 UTC
[jira] [Updated] (SOLR-14666) Cannot read ZK Kerberos conf when
enabling java security manager
[ https://issues.apache.org/jira/browse/SOLR-14666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Houston Putman updated SOLR-14666:
----------------------------------
Security: (was: Public)
> Cannot read ZK Kerberos conf when enabling java security manager
> ----------------------------------------------------------------
>
> Key: SOLR-14666
> URL: https://issues.apache.org/jira/browse/SOLR-14666
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 8.6
> Reporter: Jörn Franke
> Priority: Major
>
> {color:#222222}When activating the Java security manager then Solr cannot use anymore the jaas-client conf specified via java.security.auth.login.conf with Zookeeper. We have configured Kerberos authentication for Zookeeper.{color}
> {color:#222222}When disabling java security manager it works perfectly fine.{color}
> {color:#222222}The exact error message is : „No JAAS configuration section named 'Client' was found“. Somehow it seems that the Java security manager blocks access to that file .{color}
> {color:#222222}The directory for the file is in the -Dsolr.allowPaths{color}
> {color:#222222} Could this be a bug or is it a misconfiguration?{color}
>
> {color:#222222}Maybe a policy file is missing in Solr?{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org