You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Joel Bernstein (Jira)" <ji...@apache.org> on 2019/12/06 01:55:00 UTC

[jira] [Comment Edited] (SOLR-14014) Allow Solr to start with Admin UI disabled

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

Joel Bernstein edited comment on SOLR-14014 at 12/6/19 1:54 AM:
----------------------------------------------------------------

The problem is the timing on SOLR-13987. Do we have a commitment from someone to step up and do it? It's going to take someone rolling up their sleeves and digging into Angular.

One option on this ticket is to have headless mode not be the default. This would allow people choose headless if security overrides the convenience of the admin. Right now people have no choice but just to accept the insecure admin.

 

 

 


was (Author: joel.bernstein):
The problem is the timing on SOLR-13987. Do we have a commitment from someone to step up and do it? It's going to take someone rolling up their sleeves and digging into Angular.

One option on this ticket is to have headless mode not be the default. This would allow people choose headless if security overrides the convenience of the admin. Right now we have no choice but just to accept the insecure admin.

 

 

 

> Allow Solr to start with Admin UI disabled
> ------------------------------------------
>
>                 Key: SOLR-14014
>                 URL: https://issues.apache.org/jira/browse/SOLR-14014
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Admin UI, security
>    Affects Versions: master (9.0), 8.3.1
>            Reporter: Jason Gerlowski
>            Priority: Major
>
> Currently Solr always runs the Admin UI. With the history of XSS issues and other security concerns that have been found in the Admin UI, Solr should offer a mode where the Admin UI is disabled. Maybe, and this is a topic that'll need some serious discussion, this should even be the default when Solr starts.
> NOTE: Disabling the Admin UI removes XSS and other attack vectors. But even with the Admin UI disabled, Solr will still be inherently unsafe without firewall protection on a public network.
> *Proposed design:*
> A java system property called *headless* will be used as an internal flag for starting Solr in headless mode. This property will default to true. A java property can be used at startup to set this flag to false.
> Here is an example:
> {code:java}
>  bin/solr start -Dheadless=false {code}
> A message will be added following startup describing the mode.
> In headless mode the following message will be displayed:
> "solr is running in headless mode. The admin console is unavailable. To to turn off headless mode and allow the admin console use the following parameter startup parameter:
> -Dheadless=false 
>   
> In non-headless mode the following message will be displayed:
> "solr is running with headless mode turned off. The admin console is available in this mode. Disabling the Admin UI removes XSS and other attack vectors"  
> If a user attempts to access the admin console while Solr is in headless mode it Solr will return 401 unauthorized.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org