[
https://issues.apache.org/jira/browse/KNOX-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15740331#comment-15740331
]
Larry McCay commented on KNOX-805:
----------------------------------
[~treydone] - this sounds good.
I may even take it a little farther and say that the username, password can be
added to the connectionContext as well.
Oh - and call it connectionContext. :)
The method Hadoop.login(url, user,password) will call Hadoop.login(url,
httpclientconfiguration) using a default httpclientconfiguration.
This allows for new authentication challenge types which I planned to do anyway
- such as using a token that was acquired via some external knoxinit type call
which persists a token in a permissions protected file. See #2 in KIP-4
(https://cwiki.apache.org/confluence/display/KNOX/KIP-4+KnoxShell+Improvements)
for more details.
> Allow defining a custom HttpClient when creating a new session
> --------------------------------------------------------------
>
> Key: KNOX-805
> URL: https://issues.apache.org/jira/browse/KNOX-805
> Project: Apache Knox
> Issue Type: Bug
> Components: ClientDSL
> Reporter: Vincent Devillers
> Assignee: Vincent Devillers
>
> When creating a new session, I think it should be possible to specify a
> custom CloseableHttpClient in parameter of the static method
> Hadoop.login(url, user,password). This will allow to prepare a well defined
> CloaseableHttpClient if you want to add headers, limit the length of the
> message send, define specific strategy on dns resolution or hostname
> verification, size the connection pool…
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
