You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "liseli (via GitHub)" <gi...@apache.org> on 2024/08/05 19:49:49 UTC
Re: [I] Solrcloud pods not starting with custom security.json [solr-operator]
liseli commented on issue #594:
URL: https://github.com/apache/solr-operator/issues/594#issuecomment-2269796448
Hi team,
I've set up Solr authentication defining my **security.json**. I have created two secrets (**fulltext-solrcloud-basic-auth => type kubernetes.io/basic-auth and solr-security-json => Opaque**.Both secrets exist in the same YAML file, but in Kubernetes, two separate secrets are created. The cluster starts without issue, however, the Solr Admin UI has the **Warning: Security is not enabled for this server!**
This is how the authentication looks in the solr_specs.
```
solrSecurity:
authenticationType: Basic
basicAuthSecret: fulltext-solrcloud-basic-auth
bootstrapSecurityJson:
name: solr-security-json
key: security.json
```
If I only do `authenticationType: Basic`, everything works fine, then I guess there is something wrong with my files. I am trying to create my security.json file because I want to create additional users in my Solr clusters.
Thanks in advance!
--
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: issues-unsubscribe@solr.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org