solr
solr copied to clipboard
SOLR-17724: adding a script on how to calculated the encoded password format
https://issues.apache.org/jira/browse/SOLR-17724
Description
Adding a short bash script in the documentation that illustrates how to calculate the encoded password format for security.json
Solution
doc
Tests
doc only
Checklist
Please review the following and check all that apply:
- [v ] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
- [ ] I have created a Jira issue and added the issue ID to my pull request title.
- [ ] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended, not available for branches on forks living under an organisation)
- [ v] I have developed this patch against the
mainbranch. - [ ] I have run
./gradlew check. - [ ] I have added tests for my changes.
- [ v] I have added documentation for the Reference Guide
@elangelo thanks for this... However, I am wondering if we need to go a bit furthur...
@janhoy you often have good ideas on if something is the right way...
I am wondering, do we need to tweak out bin/solr auth command to basically do what this script does? Have a cross platform no custom coding option?
Thoughts from either of you (or anyone else?)
+1 to a bin/solr auth encode-pass or similar in Java code. Or simply link to https://clemente-biondo.github.io/ or even embed the js as a tool on the solr website itself?
I did some JIRA gardening and linking this.
@elangelo would you be interestedin picking up @janhoy idea of tweaking the AuthTool to handle the encoding? I'd prefer not to add another bash based tool, and stick to Java...
@elangelo would you be interestedin picking up @janhoy idea of tweaking the AuthTool to handle the encoding? I'd prefer not to add another bash based tool, and stick to Java...
I'm not into java at all... I don't even have an idea how to start this. I'm not saying no... but certainly right now it's kind of hard to fit timewise.
This PR has had no activity for 60 days and is now labeled as stale. Any new activity will remove the stale label. To attract more reviewers, please tag people who might be familiar with the code area and/or notify the [email protected] mailing list. To exempt this PR from being marked as stale, make it a draft PR or add the label "exempt-stale". If left unattended, this PR will be closed after another 60 days of inactivity. Thank you for your contribution!
This PR is now closed due to 60 days of inactivity after being marked as stale. Re-opening this PR is still possible, in which case it will be marked as active again.