[
https://issues.apache.org/jira/browse/SOLR-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358348#comment-14358348
]
Jan Høydahl commented on SOLR-7230:
-----------------------------------
This issue lacks a lot of context and high level end user focus. The area of
security has been something we have avoided in our code base until now - for a
reason - and this Jira seems to want to rush something home-cooked in without a
bigger plan. Sort of starting in the wrong end.
I think time may be ripe for adding security and user login to stock Solr. It
will further solidify Solr as the choice for the enterprise.
The area of security is big and with many external integration needs. I think
we should create an umbrella Jira outlining a master plan for what it takes to
secure Solr and what our user's most urgent needs are. Then sub-tasks will
follow.
What is your concrete use case that triggered this Jira, Noble?
> An API to plugin security into Solr
> -----------------------------------
>
> Key: SOLR-7230
> URL: https://issues.apache.org/jira/browse/SOLR-7230
> Project: Solr
> Issue Type: New Feature
> Reporter: Noble Paul
>
> The objective is to define a API that a plugin can implement to protect
> various operations performed on Solr. It may have various implementations .
> Some built in and some external.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
