You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hc.apache.org by "Oleg Kalnichevski (Jira)" <ji...@apache.org> on 2023/05/07 12:12:00 UTC

[jira] [Resolved] (HTTPCLIENT-1962) WindowsNegotiateScheme incorrectly requires challenge in initial response

     [ https://issues.apache.org/jira/browse/HTTPCLIENT-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski resolved HTTPCLIENT-1962.
-------------------------------------------
    Fix Version/s:     (was: Stuck)
       Resolution: Won't Fix

NTML scheme has been deprecated and is no longer supported.

Oleg

> WindowsNegotiateScheme incorrectly requires challenge in initial response
> -------------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-1962
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1962
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient (Windows)
>    Affects Versions: 5.0 Beta3
>            Reporter: Volker Jung
>            Priority: Major
>              Labels: stuck, volunteers-wanted
>
> 'WindowsNegotiateScheme.processChallenge' requires the value of an AuthChallenge to be present on any invocation, as it requires the GSSAPI-Data to perform the authentication process.
> But the "WWW-Authenticate"-header of the initial "401 Unauthorized" response does not contain any GSSAPI-Data (see [RFC4559|https://tools.ietf.org/html/rfc4559#page-2], Section 4.1, first paragraph).
> 'WindowsNegotiateScheme.generateAuthResponse' correctly handles the initial case, as it does not require any challenge to be present.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org