[ https://issues.apache.org/jira/browse/SOLR-8440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002316#comment-16002316 ]
Ishan Chattopadhyaya commented on SOLR-8440: -------------------------------------------- The bin/solr script has no notion of SOLR_VAR_DIR. I'm not familiar with the bin/install_solr_service.sh, which has the SOLR_VAR_DIR. Can you please advice how to proceed, or cook up a patch for this? Also, I can look at it myself, but I might miss the 6.6 release branch cutoff. But, maybe, this is fine to fix even after release branch is cut. > Script support for enabling basic auth > -------------------------------------- > > Key: SOLR-8440 > URL: https://issues.apache.org/jira/browse/SOLR-8440 > Project: Solr > Issue Type: New Feature > Components: scripts and tools > Reporter: Jan Høydahl > Assignee: Ishan Chattopadhyaya > Labels: authentication, security > Fix For: 6.6, master (7.0) > > Attachments: SOLR-8440.patch, SOLR-8440.patch, SOLR-8440.patch, > SOLR-8440.patch, SOLR-8440.patch, SOLR-8440.patch, SOLR-8440.patch, > SOLR-8440.patch > > > Now that BasicAuthPlugin will be able to work without an AuthorizationPlugin > (SOLR-8429), it would be sweet to provide a super simple way to "Password > protect Solr"™ right from the command line: > {noformat} > bin/solr basicAuth -adduser -user solr -pass SolrRocks > {noformat} > It would take the mystery out of enabling one single password across the > board. The command would do something like this > # Check if HTTPS is enabled, and if not, print a friendly warning > # Check if {{/security.json}} already exists > ## NO => create one with only plugin class defined > ## YES => Abort if exists but plugin is not {{BasicAuthPlugin}} > # Using security REST API, add the new user -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org