[ 
https://issues.apache.org/jira/browse/SOLR-14216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272456#comment-17272456
 ] 

Anshum Gupta commented on SOLR-14216:
-------------------------------------

After having thought more about this, and realizing the importance of this, I 
think this will provide a lot of value to users.

Sorry about the back and forth, [~janhoy] .

> 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
>            Assignee: Jan Høydahl
>            Priority: Major
>          Time Spent: 20m
>  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)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to