[
https://issues.apache.org/jira/browse/SOLR-14216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17301475#comment-17301475
]
Jan Høydahl edited comment on SOLR-14216 at 3/15/21, 8:10 AM:
--------------------------------------------------------------
Ok, so seems like there is some support for this idea. Feel free to grab it
Eric.
But I think the linked PR is just a draft, better consider a cleaner approach
like [my comment|#comment-17071277] from March 30th.
was (Author: janhoy):
Ok, so seems like there is some support for this idea. Feel free to re-open it
Eric.
But I think the PR is just a draft, better consider a cleaner approach like [my
comment|#comment-17071277] from March 30th.
> Exclude HealthCheck from authentication
> ---------------------------------------
>
> Key: SOLR-14216
> URL: https://issues.apache.org/jira/browse/SOLR-14216
> Project: Solr
> Issue Type: Improvement
> Components: Authentication
> Reporter: Jan Høydahl
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{HealthCheckHandler}} on {{/api/node/health}} and
> {{/solr/admin/info/health}} should by default not be subject to
> authentication, but be open for all. This allows for load balancers and
> various monitoring to probe Solr's health without having to support the auth
> scheme in place. I can't see any reason we need auth on the health endpoint.
> It is possible to achieve the same by setting blockUnknown=false and
> configuring three RBAC permissions: One for v1 endpoint, one for v2 endpoint
> and one "all" catch all at the end of the chain. But this is cumbersome so
> better have this ootb.
> An alternative solution is to create a separate HttpServer for health check,
> listening on a different port, just like embedded ZK and JMX.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
