[jira] [Commented] (SOLR-7890) By default require admin rights to access /security.json in ZK

["Jan Høydahl (JIRA)" <ji...@apache.org>]

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

Jan Høydahl commented on SOLR-7890:
-----------------------------------

Protecting {{/security.json}} from client users does not really solve anything as long as Admin UI shows all ZK content to all authenticated users. I see two options to solve this
1) Short-term we disable showing of {{security.json}} via Admin UI entirely
2) Long-term after Admin UI is password protected (SOLR-7896), hide the sensitive nodes depending on who is logged in.

What do you think?

> By default require admin rights to access /security.json in ZK
> --------------------------------------------------------------
>
>                 Key: SOLR-7890
>                 URL: https://issues.apache.org/jira/browse/SOLR-7890
>             Project: Solr
>          Issue Type: Sub-task
>          Components: security
>            Reporter: Jan Høydahl
>             Fix For: Trunk
>
>
> Perhaps {{VMParamsAllAndReadonlyDigestZkACLProvider}} should by default require admin access for read/write of {{/security.json}}, and other sensitive paths. Today this is left to the user to implement.
> Also, perhaps factor out the already-known sensitive paths into a separate class, so that various {{ACLProvider}} implementations can get a list of paths that should be admin-only, read-only etc from one central place. Then 3rd party impls pulling ZK creds from elsewhere will still do the right thing in the future if we introduce other sensitive Znodes...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org