[
https://issues.apache.org/jira/browse/SOLR-14226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026880#comment-17026880
]
ASF subversion and git services commented on SOLR-14226:
--------------------------------------------------------
Commit b2d8b784a305ab06199b1e6c2ebea2025c4863eb in lucene-solr's branch
refs/heads/branch_8x from Chris M. Hostetter
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=b2d8b78 ]
New /stream test cases showing authn+authz edge cases in cloud mode
This triggers various places in the Streaming Expressions code that use
background threads
to confirm that the expected credentails (or lack of) are propogarded along.
Test currently has comments + workarounds for 2 known client issues:
- SOLR-14226: SolrStream reports AuthN/AuthZ failures (401|403) as IOException
w/o details
- SOLR-14222: CloudSolrClient converts (update) 403 error to 500 error
(cherry picked from commit 517438e356d272565ee0e33e08d0ec58f8f6cd39)
> SolrStream reports AuthN/AuthZ failures (401|403) as IOException w/o details
> ----------------------------------------------------------------------------
>
> Key: SOLR-14226
> URL: https://issues.apache.org/jira/browse/SOLR-14226
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ, streaming expressions
> Reporter: Chris M. Hostetter
> Priority: Major
>
> If you try to use the SolrJ {{SolrStream}} class to making a streaming
> expression request to a solr node, any authentication or authorization
> failures will be swallowed and a eneric "IOException" will be thrown.
> (evidently due to a pars error trying to read the body of the response w/o
> consulting the HTTP status?)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
