You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/03/17 03:02:00 UTC
[jira] [Commented] (SOLR-18048) Authn/Authz Filter
[ https://issues.apache.org/jira/browse/SOLR-18048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18066232#comment-18066232 ]
ASF subversion and git services commented on SOLR-18048:
--------------------------------------------------------
Commit 2cd2e4e5f832c8522150c65ed30f0bf4e584ad3f in solr's branch refs/heads/main from Gus Heck
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=2cd2e4e5f83 ]
SOLR-18048 Move authentication into a Servlet Filter (#4120)
> Authn/Authz Filter
> ------------------
>
> Key: SOLR-18048
> URL: https://issues.apache.org/jira/browse/SOLR-18048
> Project: Solr
> Issue Type: Sub-task
> Components: security, Server
> Reporter: Gus Heck
> Priority: Major
> Labels: pull-request-available
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> Currently our code for authentication is invoked from the top of the dispatch method. If one reads down into that code, it's actually going to singificant lengths to mimic a filter (which is what most auth libraries anticipate, it even goes so far as to create a lambda implmentation of FilterChain to satisfy our authentication plugin api (which anticipated usage as a filter).
> So, once we've got all the preceding functionality handled by filters, let's use our authentication plugin API the way it is designed to be used... as a servlet filter!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org