Bug 848814 - HTTP Router requires keystore, even when using configurations that shouldn't
HTTP Router requires keystore, even when using configurations that shouldn't
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB (Show other bugs)
5.3.0 GA
Unspecified Unspecified
low Severity unspecified
: ---
: ---
Assigned To: Kevin Conner
Depends On:
Blocks: 852816
  Show dependency treegraph
Reported: 2012-08-16 09:22 EDT by Rick Wagner
Modified: 2012-11-06 16:00 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 852816 (view as bug list)
Last Closed: 2012-11-06 15:59:23 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Rick Wagner 2012-08-16 09:22:38 EDT
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:


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 15:59:23 EST
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.

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


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