[ https://issues.apache.org/jira/browse/SOLR-9680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Høydahl reassigned SOLR-9680: --------------------------------- Assignee: Jan Høydahl > Better error messages in SolrCLI when authentication required > ------------------------------------------------------------- > > Key: SOLR-9680 > URL: https://issues.apache.org/jira/browse/SOLR-9680 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Components: scripts and tools > Reporter: Jan Høydahl > Assignee: Jan Høydahl > > Currently the status tool does not distinguish between > Authentication/Authorization errors and other IO errors and just throws a > generic Exception with the 401 HTML output from Jetty: > {noformat} > $ bin/solr status > Found 1 Solr nodes: > Solr process 4332 running on port 8983 > ERROR: Failed to get system information from http://localhost:8983/solr due > to: org.apache.http.client.ClientProtocolException: Expected JSON response > from server but received: <html> > <head> > <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/> > <title>Error 401 require authentication</title> > </head> > <body><h2>HTTP ERROR 401</h2> > <p>Problem accessing /solr/admin/info/system. Reason: > <pre> require authentication</pre></p> > </body> > </html> > Typically, this indicates a problem with the Solr server; check the Solr > server logs for more information. > {noformat} > Instead, the tool should exit with a clear message that authentication is > required, and the status tool should throw a security related exception that > tool consumers (such as assertTool) can detect. Due to this {{assert -u}} > also fails when Solr is password protected. -- 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