Bug 848814

Summary: HTTP Router requires keystore, even when using configurations that shouldn't
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Rick Wagner <rwagner>
Component: JBossESBAssignee: Kevin Conner <kevin.conner>
Status: CLOSED DEFERRED QA Contact:
Severity: unspecified Docs Contact:
Priority: low    
Version: 5.3.0 GACC: soa-p-jira
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 852816 (view as bug list) Environment:
Last Closed: 2012-11-06 20:59:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 852816    

Description Rick Wagner 2012-08-16 13:22:38 UTC 
Description of problem:
HttpRouter can be configured to use a SocketFactory that shouldn't require a keystore.  Using such a configuration results in an error at deployment time, though.

How reproducible:
Using quickstarts/https_2way_ssl, try this:

#keystore=@keystore@
#keystore-passw=https_2way_ssl_pass 

Which will result in:
org.jboss.soa.esb.ConfigurationException: Failed to locate keystore '/keystore'

Likewise, you can give the configuration a path to a null file.  This gets:
java.security.KeyStoreException: failed to extract any certificates or private keys- maybe bad password?
Comment 1 Rick Wagner 2012-11-06 20:59:23 UTC 
Fix looks less than trivial, time is short before SOA 6.

Closing this BZ so we can concentrate on higher priority issues on the 5.3 branch.

Rick
Comment 2 Rick Wagner 2012-11-06 20:59:59 UTC 
Above should say "more than trivial"....

Rick