[
https://issues.apache.org/jira/browse/SOLR-9640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15883789#comment-15883789
]
Jan Høydahl commented on SOLR-9640:
-----------------------------------
I think I might not have run the full test suite before push this time :( Need
to dig further and harden failing method to work in all circumstances.
It was the cloudConfig object that was null for a bunch of tests. In an earlier
comment on this issue I wrote
bq. Generating nodeName from host and port properties of CloudConfig, which
seems a bit odd when not running cloud...
So that was true then. Will try to pull host, port and context from env.vars
instead of from config object, and make sure that the test-runner also populate
these vars if it does not already. Or do you know any fool-proof way of
retrieving own host:port through outside of a request without peeking in the
host and jetty.port vars?
> Support PKI authentication and SSL in standalone-mode master/slave auth with
> local security.json
> ------------------------------------------------------------------------------------------------
>
> 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.5, master (7.0)
>
> Attachments: SOLR-9640.patch, SOLR-9640.patch, 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
