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 2016/03/15 16:27:33 UTC
[jira] [Resolved] (HTTPCLIENT-1712) SPNego Authentication to HTTPS
service
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCLIENT-1712.
-------------------------------------------
Resolution: Invalid
Fix Version/s: (was: 5.0 Alpha1)
Patch reverted.
Oleg
> SPNego Authentication to HTTPS service
> --------------------------------------
>
> Key: HTTPCLIENT-1712
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1712
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpAuth
> Affects Versions: 4.5.1
> Reporter: Georg Romstorfer
> Priority: Minor
> Attachments: GGSSchemeBase.patch
>
>
> When connecting with the HttpClient to a website through the HTTPS-Protocol, SPNego Authentication does not work, because in the method GGSSchemeBase#generateGSSToken is the service name hardcoded to HTTP.
> A workaround is to extend the class SPNegoScheme and override this method.
> To fix this, I think it would be best to get the protocol from the current connection, but I don't how to get the connection in this class, so I can't provide a patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org