[
https://issues.apache.org/jira/browse/SOLR-11238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16135752#comment-16135752
]
Ishan Chattopadhyaya commented on SOLR-11238:
---------------------------------------------
Hi Hrishikesh, apologies for missing this one. I'll have a detailed look by
this Friday, 25th. Sorry for the delay.
> Solr authorization plugin is not able to pass additional params downstream
> --------------------------------------------------------------------------
>
> Key: SOLR-11238
> URL: https://issues.apache.org/jira/browse/SOLR-11238
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 6.6
> Reporter: Hrishikesh Gadre
> Attachments: SOLR-11238.patch
>
>
> Authorization checks in Solr are implemented by invoking configured
> authorization plugin with AuthorizationContext object. The plugin is expected
> to return an AuthorizationResponse object which provides the result (which
> can be OK/FORBIDDEN/PROMPT).
> In some cases (e.g. document level security implemented in Apache Sentry), it
> is useful for the authorization plugin to add (or override) the request
> parameters sent by the user (which are represented as SolrParams in
> [AuthorizationContext|
> https://github.com/apache/lucene-solr/blob/3cbbecca026eb2a9491fa4a24ecc2c43c26e58bd/solr/core/src/java/org/apache/solr/security/AuthorizationContext.java#L38]).
> This jira is to introduce an ability to customize the parameters by the
> authorization plugin.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
