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

Oleg Kalnichevski resolved HTTPCLIENT-1896.
-------------------------------------------
    Resolution: Won't Fix

GGS based experimental scheme have been deprecated and are no longer supported.

Oleg

> GGSSchemeBase does not support GSS continuation
> -----------------------------------------------
>
>                 Key: HTTPCLIENT-1896
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1896
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpClient (classic)
>    Affects Versions: 4.5.2
>         Environment: IBM Java
>            Reporter: Jan Kalina
>            Priority: Major
>
> GGSSchemeBase suppose only one challenge exchange is correct - if server 
> requires continuation (for example when running on IBM java), it is rejected 
> by GGSSchemeBase:
> *Authentication already attempted*
> This is caused by following part of GGSSchemeBase:
> {code:java}
>         if (state == State.UNINITIATED) {
>             token = Base64.decodeBase64(challenge.getBytes());
>             state = State.CHALLENGE_RECEIVED;
>         } else {
>             log.debug("Authentication already attempted");
>             state = State.FAILED;
>         }
> {code}
> This is not sufficient for IBM java, which use workflow:
> C -> S (initial, no negotiate header)
>  C <- S (client receive first challenge)
>  C -> S (client send first response)
>  C <- S (Oracle would already sent OK, but IBM sends second challenge!) <- 
> httpclient fails
>  C -> S (client sends second response)
>  C <- S (client receive requested page - OK)



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

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

Reply via email to