IS team correct me if I am wrong. We encountered similar kind of behavior
recently. My only explanation is we are using wso2carbon.jks which contains
a self signed cert and it will be trusted based on signed hostname.

Thanks & Regards
Danushka Fernando
Software Engineer
WSO2 inc. http://wso2.com/
Mobile : +94716332729


On Tue, Mar 18, 2014 at 5:21 AM, Nadeeshaan Gunasinghe
<[email protected]>wrote:

> Hi all,
> I am trying to create SSL Profiles in wso2esb-4.8.1. Here are my axis2.xml
> entry for the SSL Profile
>
> *<transportSender name="https"
>>> class="org.apache.synapse.transport.passthru.PassThroughHttpSSLSender">*
>>
>> *        <parameter name="non-blocking" locked="false">true</parameter>*
>>
>> *        <parameter name="customSSLProfiles">*
>>
>> *        <profile>*
>>
>> *        <servers>localhost:9444</servers>*
>>
>> *        <TrustStore>*
>>
>> *
>>>  <Location>repository/resources/security/client-truststore.jks</Location>*
>>
>> *                <Type>JKS</Type>*
>>
>> *                <Password>wso2carbon</Password>*
>>
>> *            </TrustStore>*
>>
>> *    </profile>*
>>
>> *           <profile>*
>>
>> *               <servers>10.100.4.80:9445
>>> <http://10.100.4.80:9445></servers>*
>>
>> *               <KeyStore>*
>>
>> *
>>>  <Location>repository/resources/security/wso2carbon.jks</Location>*
>>
>> *                <Type>JKS</Type>*
>>
>> *                <Password>wso2carbon</Password>*
>>
>> *                <KeyPassword>wso2carbon</KeyPassword>*
>>
>> *            </KeyStore>*
>>
>> *               <TrustStore>*
>>
>> *
>>>  <Location>repository/resources/security/client-truststore.jks</Location>*
>>
>> *                <Type>JKS</Type>*
>>
>> *                <Password>wso2carbon</Password>*
>>
>> *            </TrustStore>*
>>
>> *           </profile>*
>>
>> *      </parameter>*
>>
>> *        <parameter name="HostnameVerifier">AllowAll</parameter>*
>>
>> *    </transportSender>*
>>
>>
> In  *10.100.4.80:9445 <http://10.100.4.80:9445> *runs the echo service in
> wso2 dss. I created a proxy service which points to the echo service and
> accessing the echo service via the proxy created in ESB.
> My problem is
>
>
>    1. When I change the target server to *10.100.4.81:9445
>    <http://10.100.4.81:9445> * esb proxy can communicate with the echo
>    service without any problem. Why does this happen?
>
>
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to