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

Jan Høydahl commented on SOLR-9640:
-----------------------------------

I quickly tested Solr with and without SSL. By default Jetty listen on the same 
port (8983) for both. A server started in SSL mode will send empty response if 
it receives a plain http request:
{code}
$ curl http://localhost:8983/solr/
curl: (52) Empty reply from server
{code}
And the other way - trying a https request to port 8983 on a non-SSL Solr will 
return an error:
{code}
$ curl https://localhost:8983/solr/
curl: (35) Unknown SSL protocol error in connection to localhost:-9847
{code}

Anyway, this is probably a discussion for another JIRA. In the context of this 
one I'm more looking for feedback on the choice of detecting urlScheme when we 
don't have ZK around.

> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to