Bug 797746 - HttpProtocol should use default keystore location if not specified
Summary: HttpProtocol should use default keystore location if not specified
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.2.0 GA
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-27 08:16 UTC by Martin Weiler
Modified: 2021-10-15 11:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Enhancement
Embargoed:


Attachments (Terms of Use)

Description Martin Weiler 2012-02-27 08:16:40 UTC
Description of problem:
Using HttpRouter to connect to https:// requires to specify information about the ssl key. If the keystore location is not explicitly defined, '/keystore' is used as default location.

This default location should be changed to use the default JRE keystore location - ${JAVA_HOME}/lib/security/cacerts


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

How reproducible:
Always

Steps to Reproduce:
1. Set up HttpRouter with https:// target endpoint
2. Don't explicitly  set the "keystore" property
  
Actual results:
Initialization fails:

Caused by: org.jboss.soa.esb.ConfigurationException: Failed to locate keystore '/keystore'.
        at org.jboss.soa.esb.http.configurators.HttpProtocol.getKeyMaterial(HttpProtocol.java:200)
        at org.jboss.soa.esb.http.configurators.HttpProtocol.configure(HttpProtocol.java:94)
        at org.jboss.soa.esb.http.HttpClientFactory.createHttpClient(HttpClientFactory.java:84)
        at org.jboss.soa.esb.actions.routing.http.HttpRouter.<init>(HttpRouter.java:113)


Expected results:
Initialization succeeds by using the default keystore location. An INFO message could inform the user that the default keystore is used.


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