gus-asf commented on code in PR #3301: URL: https://github.com/apache/solr/pull/3301#discussion_r2223447083
########## solr/solr-ref-guide/modules/deployment-guide/pages/basic-authentication-plugin.adoc: ########## @@ -81,6 +81,14 @@ If `realm` is not defined, it will default to `solr`. If you are using SolrCloud, you must upload `security.json` to ZooKeeper. An example command and more information about securing your setup can be found at xref:authentication-and-authorization-plugins#in-a-solrcloud-cluster[Authentication and Authorization Plugins In a SolrCloud Cluster]. +=== Password Encoding + +Solr stores the passwords in the format: `base64(sha256(sha256(salt+password))) base64(salt)`. + +If you edit `security.json` directly then you need to encode the password yourself. +You can visit https://clemente-biondo.github.io/ to use a simple web utility that does the encoding for you. Review Comment: I once had a client that couldn't figure out how to give me access to their solr admin ui. After multiple failed attempts and clear intent that I *should* have access, I looked up the code in Solr, executed it in an IntelliJ groovy console and generated myself a password, which I then added it to their (unsecured) zookeeper to gain access. (and advised them of what I had done and the need to secure things further). My point is, if we are going to document this, we could easily expose a tool based on our code rather than reference a 3rd party. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
