[
https://issues.apache.org/jira/browse/SOLR-13972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988875#comment-16988875
]
Ishan Chattopadhyaya commented on SOLR-13972:
---------------------------------------------
bq. We could also move the warning into Java-land and have it go to solr.log,
but that's less visible.
+1 to this option. I don't think printing on stdout is necessary.
> Insecure Solr should generate startup warning
> ---------------------------------------------
>
> Key: SOLR-13972
> URL: https://issues.apache.org/jira/browse/SOLR-13972
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Priority: Critical
> Time Spent: 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: [email protected]
For additional commands, e-mail: [email protected]
