Eric Pugh created SOLR-18611:
--------------------------------
Summary: Bootstrap a security.json as formal start option.
Key: SOLR-18611
URL: https://issues.apache.org/jira/browse/SOLR-18611
Project: Solr
Issue Type: Sub-task
Components: cli, security
Affects Versions: 10.1
Reporter: Eric Pugh
Right now there are ways of dropping a security.json into solr so you find it.
In standalone its place {{security.json}} in {{{}$SOLR_HOME{}}}, beside
{{{}solr.xml{}}}. In SolrCloud it's drop it into ZK before you start.
Both of those require deep arcane knowledge of Solr ops!
bin/solr start --bootstrap-security=../mysetup/single_user_security.json
This would allow you on start up to load a security.json that you configure
that is your starting point....
I looked at what bin/solr auth --credentials alice:MyStrongPassword and it
actually sets up a basic security.json with {{{}superadmin{}}}, {{{}admin{}}},
{{{}index{}}}, {{search }}
I could also see a bin/solr start --admin alice:MyStrongPassword that would be
similar to what bin/solr auth does.
Though maybe I would want it to be:
bin/solr start --admin solr:kfSoXXVZwU94UwjRezS0bMbzGoqG8rvECMGWXf0jzWo=
cWFwcnliMW41Z3BjcXd0aQ== ??????
I would skip the local solr.in.sh / solr.in.cmd stuff that auth does, that just
feels old school.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
