[MNG-3230] HTTPS with self-signed certificate does not work, no error message.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Affects Version/s: 2.0.7
• Component/s: Artifacts and Repositories
• Assignee: Unassigned
• Reporter: Andreas Krüger
• Created: 04/Oct/07 09:47
• Updated: 02/Jul/14 08:44
• Resolved: 22/Jan/14 20:32

Description

We have a repository server that serves the same files both via HTTPS and HTTP.

Maven is not able to find artifacts when using HTTPS. All goes well when using HTTP.

The problem probably is that the HTTPS - certificate used by the repository server is self-signed, and Maven has not been configured to accept that certificate as genuine. (This is a guess.)

Expected behavior: With HTTPS, build does not continue. Maven gives an error message indicating the problem is certificate-related.

Behavior seen: Maven reacts as if there were no problem connecting the repository, but as if the artifact were missing from the repository. It continues to search other repositories as happen to be configured. (However, the artifact is clearly there, e.g., can be downloaded with "wget --no-check-certificate " via HTTPS.)