[
https://issues.apache.org/jira/browse/SOLR-9640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15611820#comment-15611820
]
Shalin Shekhar Mangar commented on SOLR-9640:
---------------------------------------------
bq. And wrt detecting urcScheme, I wonder why SolrCloud needs a clusterProp for
this? Could not each node assume https if solr.jetty.keystore is set, that
would be one less thing to configure...
Say if we detected https by looking at solr.jetty.keystore, my guess (untested)
is that adding a wrongly configured node (no SSL) to the cloud will still work
and all other nodes would be able to talk to this one node without https. So a
global configuration saying everything must be https is necessary.
> Support PKI authentication in standalone mode
> ---------------------------------------------
>
> Key: SOLR-9640
> URL: https://issues.apache.org/jira/browse/SOLR-9640
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: security
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Labels: authentication, pki
> Fix For: 6.x, master (7.0)
>
> Attachments: SOLR-9640.patch, SOLR-9640.patch, SOLR-9640.patch
>
>
> While working with SOLR-9481 I managed to secure Solr standalone on a
> single-node server. However, when adding
> {{&shards=localhost:8081/solr/foo,localhost:8082/solr/foo}} to the request, I
> get 401 error. This issue will fix PKI auth to work for standalone, which
> should automatically make both sharding and master/slave index replication
> work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
