[
https://issues.apache.org/jira/browse/SOLR-9727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644001#comment-15644001
]
Jan Høydahl commented on SOLR-9727:
-----------------------------------
Skimming your patch, I don't see the point in renaming the Java Property
everywhere? Why should there be a problem using camel-case in
{{solr.jetty.ssl.needClientAuth}}, as long as it is consistent between the
start script and {{jetty-ssl.xml}}.
Also you list 6.3 as affects version, but that version is not released. Did you
mean 5.3?
> solr.in.sh properties does not set the correct values.
> ------------------------------------------------------
>
> Key: SOLR-9727
> URL: https://issues.apache.org/jira/browse/SOLR-9727
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Server
> Affects Versions: 6.3
> Reporter: Michael Suzuki
> Assignee: Michael Suzuki
> Attachments: SOLR-9727.patch
>
>
> When setting values to true on SOLR_SSL_NEED_CLIENT_AUTH or
> SOLR_SSL_WANT_CLIENT_AUTH, jetty starts with these values as set to false.
> {code}
> SOLR_SSL_NEED_CLIENT_AUTH=true
> SOLR_SSL_WANT_CLIENT_AUTH=false
> {code}
> To recreate the issue:
> 1) Edit solr.ini.sh to enable ssl and set SOLR_SSL_NEED_CLIENT_AUTH to true.
> 2) Start solr with remote debugging.
> 3) Set a debug point in SSLContextFactory.java, on setNeedClientAuth(...)
> Expected value for needClientAuth should be true instead its false.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
