[jira] [Updated] (HTTPCLIENT-1182) Add a constructor to org.apache.http.conn.ssl.SSLSocketFactory to allow for directly wrapping a javax.net.ssl.SSLSocketFactory socketfactory
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Claassen updated HTTPCLIENT-1182: -- Remaining Estimate: 0h (was: 48h) Original Estimate: 0h (was: 48h) > Add a constructor to org.apache.http.conn.ssl.SSLSocketFactory to allow for > directly wrapping a javax.net.ssl.SSLSocketFactory socketfactory > > > Key: HTTPCLIENT-1182 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1182 > Project: HttpComponents HttpClient > Issue Type: New Feature > Components: HttpClient >Affects Versions: 4.1.3, 4.2 Beta1 >Reporter: Mark Claassen > Labels: SSLSocketFactory, Webstart, patch > Fix For: 4.1.3 > > Attachments: output > > Original Estimate: 0h > Remaining Estimate: 0h > > Our application use Java Webstart for deployment. Amoung other things, > Webstart gives us the ability to access the system's (in our case, Windows) > certificate system. For instance, one of our client is using certificate > based authentication to their webserver. This is done through a hardware > device they attach to their system. Window's already has a way to interface > with this device, and Webstart has a way to interface with the Windows API. > I don't think we can get by with using any SocketFactory that we create. (We > would have to check with Oracle to be sure.) I think we need to use the one > that is set as the default in HttpsURLConnection. > What I am suggesting is that another constructor be added to allow for just > wrapping this one. I was not planning on putting a dependancy on > HttpsURLConnection, but rather just add the ability to wrap any > javax.net.ssl.SSLSocketFactory. > This will not be a big change to the API. I will get a patch ready soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (HTTPCLIENT-1182) Add a constructor to org.apache.http.conn.ssl.SSLSocketFactory to allow for directly wrapping a javax.net.ssl.SSLSocketFactory socketfactory
[ https://issues.apache.org/jira/browse/HTTPCLIENT-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Claassen updated HTTPCLIENT-1182: -- Attachment: output > Add a constructor to org.apache.http.conn.ssl.SSLSocketFactory to allow for > directly wrapping a javax.net.ssl.SSLSocketFactory socketfactory > > > Key: HTTPCLIENT-1182 > URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1182 > Project: HttpComponents HttpClient > Issue Type: New Feature > Components: HttpClient >Affects Versions: 4.1.3, 4.2 Beta1 >Reporter: Mark Claassen > Labels: SSLSocketFactory, Webstart, patch > Fix For: 4.1.3 > > Attachments: output > > Original Estimate: 48h > Remaining Estimate: 48h > > Our application use Java Webstart for deployment. Amoung other things, > Webstart gives us the ability to access the system's (in our case, Windows) > certificate system. For instance, one of our client is using certificate > based authentication to their webserver. This is done through a hardware > device they attach to their system. Window's already has a way to interface > with this device, and Webstart has a way to interface with the Windows API. > I don't think we can get by with using any SocketFactory that we create. (We > would have to check with Oracle to be sure.) I think we need to use the one > that is set as the default in HttpsURLConnection. > What I am suggesting is that another constructor be added to allow for just > wrapping this one. I was not planning on putting a dependancy on > HttpsURLConnection, but rather just add the ability to wrap any > javax.net.ssl.SSLSocketFactory. > This will not be a big change to the API. I will get a patch ready soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
