Bug 1180941 - RFE: auto import missing SSL certificates to keystore
Summary: RFE: auto import missing SSL certificates to keystore
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Zanata
Classification: Retired
Component: Component-zanata-client
Version: 3.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Damian Jansen
QA Contact: Zanata-QA Mailling List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-12 01:15 UTC by Patrick Huang
Modified: 2015-07-28 23:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-07-28 23:18:22 UTC
Embargoed:


Attachments (Terms of Use)

Description Patrick Huang 2015-01-12 01:15:32 UTC
Description of problem:
When connecting to a https server, if the certificate is not in keystore, it will fail with exception:
javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: 
PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: 
unable to find valid certification path to requested target

Version-Release number of selected component (if applicable):
3.4.0-

How reproducible:
Always

Steps to Reproduce:
1. Make a self signed certificate and deploy to a test server
2. Try to connect to it using zanata client

Actual results:
SSLHandshakeException

Expected results:
Prompt the server certificate digest etc and ask if the user trust it and willing to add it to the keystore (maybe password protected). If user agrees then import the certificate chain to the store.

Additional Information:
Code sample that may be borrowed: 
https://code.google.com/p/java-use-examples/source/browse/trunk/src/com/aw/ad/util/InstallCert.java

Additional info:

Comment 2 Isaac Rooskov 2015-04-23 01:55:33 UTC
Please make this happen :)

Comment 3 Zanata Migrator 2015-07-28 23:18:22 UTC
Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-104


Note You need to log in before you can comment on or make changes to this bug.