Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 321975 - Cannot connect with https update site
Summary: Cannot connect with https update site
Status: RESOLVED WORKSFORME
Alias: None
Product: ECF
Classification: RT
Component: ecf.filetransfer (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: ecf.core-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-06 07:58 EDT by Wojciech Galanciak CLA
Modified: 2014-02-14 14:44 EST (History)
3 users (show)

See Also:

Attachments
error (23.82 KB, image/jpeg)
2010-08-06 07:58 EDT, Wojciech Galanciak CLA 		no flags Details
error2 (23.37 KB, image/jpeg)
2010-08-06 08:01 EDT, Wojciech Galanciak CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Wojciech Galanciak CLA 2010-08-06 07:58:41 EDT 
Created attachment 176027 [details]
error

Customer has update site to distribute updates inside a company. Since they have changed it from http to https they cannot connect with it. They have an error (error.jpg). We have tried to add certificate to jvm certificate keystore. After that they have different error (error2.jpg). Update site is correct. Certificate added to keystore was downloaded bu Firefox. Eclipse version is 3.4.2.
Comment 1 Wojciech Galanciak CLA 2010-08-06 08:01:57 EDT 
Created attachment 176028 [details]
error2
Comment 2 Scott Lewis CLA 2010-08-06 09:52:47 EDT 
The error in attachment 176028 [details] (the error after adding the certificate to cert store), seems to indicate that the certificate hostname may be wrong (i.e. not a match with what is in the certificate).  Is this inaccurate?
Comment 3 Wojciech Galanciak CLA 2010-08-06 10:18:50 EDT 
Common Name in certificate is the same as host in url.
Comment 4 Scott Lewis CLA 2010-08-06 10:46:14 EDT 
Some questions to help diagnose:  
What version of VM is being used?  What type of cert is it?  Is it a self-signed cert?  What web server (and version) are being used?

I'm adding Thomas Watson to this bug so that he can identify someone familiar with the ssl/socketfactory/trust manager code.  This code (i.e. the ECF fragments with .ssl in suffix) was contributed by IBM, and if this error is some ECF code problem (as opposed to a certificate and/or configuration problem) that someone more familiar with this code than I am will probably have to address it.
Comment 5 Thomas Watson CLA 2010-08-06 15:00:43 EDT 
Adding Matt to the list.  Matt you have any insight to what is going on?
Comment 6 Scott Lewis CLA 2014-02-14 14:44:44 EST 
Resolving this as worksforme as we can't reproduce.   Please reopen if still a problem, with more details on environment (e.g. answers to comment 4 and as much other info as possible).