You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Larry McCay (JIRA)" <ji...@apache.org> on 2016/10/21 12:35:58 UTC
[jira] [Commented] (HTTPCLIENT-1712) SPNego Authentication to HTTPS
service
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594956#comment-15594956 ]
Larry McCay commented on HTTPCLIENT-1712:
-----------------------------------------
[~olegk], [~fschumacher] - I am encountering this in the field now as we shipped Apache Knox with a dependency on 4.5.2 and can no longer dispatch requests to Hadoop APIs in a secure cluster that have SSL enabled. In addition, the use of our SSO functionality will be hampered due to the fact that our cookie must be set to secure only.
This we need a 4.5.3 to address as soon as possible.
> SPNego Authentication to HTTPS service
> --------------------------------------
>
> Key: HTTPCLIENT-1712
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1712
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> 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