[
https://issues.apache.org/jira/browse/SOLR-13972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176096#comment-17176096
]
Jan Høydahl commented on SOLR-13972:
------------------------------------
I think the technically correct way is to open a new Jira to fix the
regression, otherwise people will be confused with Jira numbers being reused in
CHANGES and it will not be clear which Solr version has a working version?
> Insecure Solr should generate startup warning
> ---------------------------------------------
>
> Key: SOLR-13972
> URL: https://issues.apache.org/jira/browse/SOLR-13972
> Project: Solr
> Issue Type: Bug
> Reporter: Ishan Chattopadhyaya
> Assignee: Jason Gerlowski
> Priority: Critical
> Fix For: master (9.0), 8.4
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Warning to the effect of, start Solr with: "solr auth enable -credentials
> solr:foo -blockUnknown true” (or some other way to achieve the same effect)
> if you want to expose this Solr instance directly to users. Maybe the link to
> the ref guide discussing all this might be in good measure here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
