Jira created
> Am 21.07.2020 um 10:28 schrieb Ishan Chattopadhyaya
> :
>
> I think this warrants a JIRA. To work around this issue for now, you can
> use an environment variable SOLR_SECURITY_MANAGER_ENABLED=false before
> starting Solr.
>
>> On Thu, Jul 16, 2020 at 11:58 PM Jörn Franke wrot
I think this warrants a JIRA. To work around this issue for now, you can
use an environment variable SOLR_SECURITY_MANAGER_ENABLED=false before
starting Solr.
On Thu, Jul 16, 2020 at 11:58 PM Jörn Franke wrote:
> The solution would be probably a policy file shipped with Solr that allows
> the ZK
The solution would be probably a policy file shipped with Solr that allows
the ZK jar to create a logincontext. I suggest that Solr ships it otherwise
one would need to adapt it for every Solr update manually to include the
version of the ZK jar.
On Thu, Jul 16, 2020 at 8:15 PM Jörn Franke wrote:
I believe it is a bug in Solr because we need to create a policy to allow
creating a login context:
See here chapter "Running the Code with a Security Manager"
http://www.informatik.hs-furtwangen.de/doku/java/j2sdk-1_4_1-doc/guide/security/jaas/tutorials/LoginConfigFile.html
Please confirm and I w
Hallo,
I am using Solr 8.6.0.
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.
When disabling java security manager it works perfectly
