[
https://issues.apache.org/jira/browse/HTTPCLIENT-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17494264#comment-17494264
]
Logan edited comment on HTTPCLIENT-2205 at 2/17/22, 10:23 PM:
--------------------------------------------------------------
> I have no idea how your application works or what it is supposed to do. Do
> your users have a private key they use to authenticate with the server?
Here are the steps in app.
# User uploaded a key store which contains private keys
# App need to call user specified url with a private key matched by user
specified alias. The results will be shown back to user. User manages to add
public key to the target server trust-store setup so we are not worried about it
Currently we are managing this by creating new SSL context and pass it new
HttpClient for every request. We don't need connection pooling since it is not
required and it's okay with performance cost of creating connection every time.
Async support is definitely beneficial here.
> There is nothing stopping you from building a non-pooling async connection
> manager.
It's not something fainted hearted like me can do. Sorry!
was (Author: logan007):
> I have no idea how your application works or what it is supposed to do. Do
> your users have a private key they use to authenticate with the server?
Here are the steps in app.
# User uploaded a key store which contains private keys
# App need to call user specified url with a private key matched by user
specified alias. The results will be shown back to user. User manages to add
public key to the target server trust-store setup so we are not worried about it
> There is nothing stopping you from building a non-pooling async connection
> manager.
It's not something fainted hearted like me can do. Sorry!
> Ability to set SSL Context and hence Keystore for every request
> ---------------------------------------------------------------
>
> Key: HTTPCLIENT-2205
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2205
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Affects Versions: 5.1, 5.1.1, 5.1.3
> Reporter: Logan
> Priority: Major
>
> With Version 4.x it easy to the SSL context and hence keystore for every
> request using the following code. How with version 5.x there is no ability to
> do this anymore. I request to enable a feature to set the SSL context (and
> hence Keystore) for every request for both synchronous and asynchronous
> clients.
> {code:java}
> SSLContext sslContext = ...
> HttpClient httpClient =
> HttpClients.custom().setSSLContext(sslContext).build();
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
