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

Jan Høydahl edited comment on SOLR-10646 at 5/9/17 11:36 AM:
-------------------------------------------------------------

Can anyone confirm my assumption about not needing 
{{$AUTHC_CLIENT_BUILDER_ARG}} and {{$SOLR_AUTHENTICATION_OPTS}} on the server 
side for *kerberos* either? If we want inter-node communication to be secured 
by Kerberos, is that config set in security.json or in AUTHC_OPTS? 
[~ichattopadhyaya] do you know?


was (Author: janhoy):
Can anyone confirm my assumption about not needing 
{{$AUTHC_CLIENT_BUILDER_ARG}} and {{$SOLR_AUTHENTICATION_OPTS}} on the server 
side for *kerberos* either? If we want inter-node communication to be secured 
by Kerberos, is that config set in security.json or in AUTHC_OPTS?

> 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]

Reply via email to