Monday, April 21, 2014

Setting up a simple WSO2 AS cluster when custom keystores are used

When we setup cluster deployments, people are reluctant to use the default keystore that is shipped with WSO2 products due to security reasons. Therefore, we can use a different keystore within our products other than what is shipped by default (wso2carbon.jks).

Lets see how this is possible and what changes we need to do in addition to the normal cluster configuration we do.

NOTE: I'm demonstrating on how to setup a simple cluster with one WSO2 Application Server Manager node and one WSO2 ELB node.

1. Download a fresh WSO2 Application Server pack from the product page. 

2. Remove the default wso2carbon.jks that is shipped with the product. This file resides in $PRODUCT_HOME/repository/resources/security folder and drop the custom keystore that you created.

keytool -genkey -alias appserverks -keyalg RSA -keystore appserver.jks -storepass appserver

3. Change the following configuration files of the App server pack so that it refers the custom keystore file.
- $PRODUCT_HOME/repository/conf/carbon.xml
- $PRODUCT_HOME/repository/conf/identity.xml

4. Follow the instructions listed under the section Configuring the Manager Node and setup the Application server manager node.

5. Follow the instructions given in WSO2 Clustering & Deployment Guide and configure a WSO2 ELB as explained in Configuring the Load Balancer section.

6. Start the WSO2 ELB node

7. Start the WSO2 Application Server node & access the Management Console and it would throw an exception as below.

[2014-04-21 23:34:40,530] ERROR - TargetHandler I/O error: General SSLEngine problem General SSLEngine problem at at at at at at org.apache.http.nio.reactor.ssl.SSLIOSession.doWrap( at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake( at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady( at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady( at org.apache.http.impl.nio.reactor.BaseIOReactor.readable( at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent( at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents( at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute( at org.apache.http.impl.nio.reactor.BaseIOReactor.execute( at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$ at
Caused by: General SSLEngine problem at at at at at at at at$ at$ at Method) at$ at org.apache.http.nio.reactor.ssl.SSLIOSession.doRunTask( at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake( ... 9 more Caused by: PKIX path building failed: unable to find valid certification path to requested target at at at at at at at ... 17 more Caused by: unable to find valid certification path to requested target at at at ... 23 more

To overcome this issue, you need to import the public certificate of the custom keystore that you used at the App server node, to the $ELB_HOME/repository/resources/security/client-truststore.jks of the WSO2 ELB instance.

Extracting the public certificate
keytool -export -alias appserverks -keystore appserver.jks -file appserverks.cert

Importing the public certificate to the client-truststore.jks of the WSO2 ELB instance

keytool -import -file appserverks.cert -keystore client-truststore.jks -storepass wso2carbon -alias appserverks

Restart the WSO2 ELB instance and then the WSO2 Appserver node and then you will be able to access the Management Console successfully

No comments: