[
https://issues.apache.org/jira/browse/CONNECTORS-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Schuch updated CONNECTORS-1693:
--------------------------------------
Description:
See external issue URL:
{quote}The underlying HTTP client of the Solr output connector always
configures a dedicated AuthScope of the connection, even if the provided realm
is the empty string (""). This is due to the fact that the attribute realm is
never null, but "" in case the user did not supply a parameter for this. This
breaks connectivity in case basic authentication is in-place, but no realm is
required. Thus, in both cases (null value and "" for realm) the HTTP client
should use AuthScope.ANY. This commit adds the necessary non-emptiness clause
to the realm check in order to fix this behavior.{quote}
was:
https://github.com/apache/manifoldcf/pull/112
{quote}The underlying HTTP client of the Solr output connector always
configures a dedicated AuthScope of the connection, even if the provided realm
is the empty string (""). This is due to the fact that the attribute realm is
never null, but "" in case the user did not supply a parameter for this. This
breaks connectivity in case basic authentication is in-place, but no realm is
required. Thus, in both cases (null value and "" for realm) the HTTP client
should use AuthScope.ANY. This commit adds the necessary non-emptiness clause
to the realm check in order to fix this behavior.{quote}
> Add non-emptiness clause to realm check of Solr output connector
> -----------------------------------------------------------------
>
> Key: CONNECTORS-1693
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1693
> Project: ManifoldCF
> Issue Type: Bug
> Reporter: Markus Schuch
> Priority: Major
>
> See external issue URL:
> {quote}The underlying HTTP client of the Solr output connector always
> configures a dedicated AuthScope of the connection, even if the provided
> realm is the empty string (""). This is due to the fact that the attribute
> realm is never null, but "" in case the user did not supply a parameter for
> this. This breaks connectivity in case basic authentication is in-place, but
> no realm is required. Thus, in both cases (null value and "" for realm) the
> HTTP client should use AuthScope.ANY. This commit adds the necessary
> non-emptiness clause to the realm check in order to fix this behavior.{quote}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
