[
https://issues.apache.org/jira/browse/SOLR-18270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18102977#comment-18102977
]
ASF subversion and git services commented on SOLR-18270:
--------------------------------------------------------
Commit 72921ecf447accdb312b8269ea3693cb32cb9de7 in solr's branch
refs/heads/branch_10x from heitzjm
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=72921ecf447 ]
SOLR-18270 CertAuthPlugin : update the lookup attribute (without
parametrization) (#4474)
Co-authored-by: Eric Pugh <[email protected]>
(cherry picked from commit 647de260b06f2903de833587af4389603e4bf42e)
> Bug in SOLR 10 CertAuthPlugin : request attribute
> --------------------------------------------------
>
> Key: SOLR-18270
> URL: https://issues.apache.org/jira/browse/SOLR-18270
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Authentication
> Affects Versions: 10.0
> Reporter: Jean-Marie HEITZ
> Assignee: Eric Pugh
> Priority: Critical
> Labels: pull-request-available
> Fix For: 10.1
>
> Time Spent: 6h 20m
> Remaining Estimate: 0h
>
> While trying to migrate from SOLR 9 to 10 using the official Docker images, I
> noticed that authentication using SSL certificates did not work anymore. I
> found out that, as I was using SOLR_SSL_NEED_CLIENT_AUTH, and that the SSL
> connection level does work and is established, the request attribute that
> carries the client cert is not "javax.servlet.request.X509Certificate"
> anymore in jetty-12, which is used in the Official SOLR Docker image : it
> became "jakarta.servlet.request.X509Certificate". I tested the attribute
> change by building SOLR and the Docker Image from source : it worked. So I
> guess it might be good to change, or add a parameter to be able to configure
> the lookup attribute in security.json.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
