[
https://issues.apache.org/jira/browse/HTTPCLIENT-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17874514#comment-17874514
]
Oleg Kalnichevski commented on HTTPCLIENT-1625:
-----------------------------------------------
> As already noted, this would require some changes in the authentication code,
> and the state machine defined in HttpAuthenticator, which may or may not
> break API compatibility.
[~stoty] I will happily help you with that. As far the rest is concerned you
are at [~michael-o] 's mercy.
> If it can be done without breaking the authentication API could it be added
> in a patch release ?
No, it could not. This feature should ideally go though the full ALPHA / BETA /
GA cycle.
> If not, how could this be delivered ?
I am afraid this is already too late for 5.4 which should go GA in September.
Oleg
> Completely overhaul GSS-API-based authentication backend
> --------------------------------------------------------
>
> Key: HTTPCLIENT-1625
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1625
> Project: HttpComponents HttpClient
> Issue Type: Task
> Components: Documentation, HttpClient (classic)
> Affects Versions: 4.5
> Reporter: Michael Osipov
> Priority: Major
> Labels: stuck, volunteers-wanted
>
> The current implementation does not reflect the way GSS-API-based
> authentication should be done. It has several design flaws.
> This is an umbrella task for:
> 1. Deprecate all old classes
> 2. Investigate how it has to be plugged into HttpClient
> 3. Reimplement from scratch
> 4. Thoroughly test all new stuff
> 5. Rewrite documentation
> Design notes are canonically available under:
> https://wiki.apache.org/HttpComponents/IssueTracking/HTTPCLIENT-1625
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
