Bug 848814 - HTTP Router requires keystore, even when using configurations that shouldn't
Summary: HTTP Router requires keystore, even when using configurations that shouldn't
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.3.0 GA
Hardware: Unspecified
OS: Unspecified
low
unspecified
Target Milestone: ---
: ---
Assignee: Kevin Conner
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 852816
TreeView+ depends on / blocked
 
Reported: 2012-08-16 13:22 UTC by Rick Wagner
Modified: 2018-11-28 19:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 852816 (view as bug list)
Environment:
Last Closed: 2012-11-06 20:59:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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


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