You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jan Høydahl (JIRA)" <ji...@apache.org> on 2015/03/11 21:10:38 UTC

[jira] [Commented] (SOLR-7230) An API to plugin security into Solr

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

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

I just became aware of Apache Shiro http://shiro.apache.org/
Instrumenting our code using a standard framework has several benefits: We don't need to maintain the core security enforcing components within Solr. Solr users can hook in their custom credentials sources; AD, LDAP, JDBC and more are supported by Shiro already. It is also not tied to Servlet containers, so we should be future proof not matter what we decide to do.

> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org