[
https://issues.apache.org/jira/browse/SOLR-10646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002840#comment-16002840
]
Ishan Chattopadhyaya commented on SOLR-10646:
---------------------------------------------
bq. If we want inter-node communication to be secured by Kerberos, is that
config set in security.json or in AUTHC_OPTS? Ishan Chattopadhyaya do you know?
Kerberos can be enabled using (example from Ref guide):
{code}
SOLR_AUTH_TYPE="kerberos"
SOLR_AUTHENTICATION_OPTS="-Djava.security.auth.login.config=/home/foo/jaas-client.conf
-Dsolr.kerberos.cookie.domain=192.168.0.107
-Dsolr.kerberos.cookie.portaware=true
-Dsolr.kerberos.principal=HTTP/[email protected]
-Dsolr.kerberos.keytab=/keytabs/107.keytab"
{code}
Reason why these can't be in security.json is because there are node specific
paths for keytab files.
> bin/solr should not pass security credentials for start command
> ---------------------------------------------------------------
>
> Key: SOLR-10646
> URL: https://issues.apache.org/jira/browse/SOLR-10646
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Fix For: 6.6, master (7.0)
>
> Attachments: SOLR-10646.patch
>
>
> Spinoff from SOLR-8440
> It is unnecessary to pass auth parameters as Java options on the cmdline for
> {{bin/solr start}}, as Solr does not need these to start, and it potentially
> exposes passwords in plain text in the UI.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
