[
https://wso2.org/jira/browse/ESBJAVA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17918#action_17918
]
indika kumara commented on ESBJAVA-493:
---------------------------------------
Hi Jonathan
I have applied your patch with some changes. Thanks Lots for your contributions.
Issue was there due to use of default URLConnection for both https and http.
Based on your patch,I fixed it . Both the private key entry store and trusted
certificate store have to be configured in synapse.properties file(In your
patch , it is in proxyservice parameters).
For example.
# KeyStores configurations
keystore.identity.location=webapp/WEB-INF/classes/conf/identity.jks
keystore.identity.type=JKS
keystore.identity.storePassword=password
keystore.identity.keyPassword=password
keystore.identity.parameters=enableHostnameVerifier=false;keyStoreCertificateFilePath=/home/esb.cer
keystore.trust.location=webapp/WEB-INF/classes/conf/trust.jks
keystore.trust.type=JKS
keystore.trust.storePassword=password
keystore.trust.parameters=enableHostnameVerifier=false;keyStoreCertificateFilePath=/home/esb.cer
All the third party certificates have to be imported to trust.jks.
I have tested proxyservice, WSDL endpoint, entry with source uri as https
location. I used WSO2WSAS as third party server.
If any scenario doesn't work , please comment this JIRA.
You may need to get fresh source check outs for both synapse and ESB.
Thanks for your contributions
Indika
> Reference PKI enabled endpoints in the Admin console
> ----------------------------------------------------
>
> Key: ESBJAVA-493
> URL: https://wso2.org/jira/browse/ESBJAVA-493
> Project: WSO2 ESB
> Issue Type: Improvement
> Components: Administration Console
> Reporter: Jonathan Holmes
> Assignee: indika kumara
> Fix For: FUTURE
>
> Attachments: Enable ESB PKI Certificates.zip,
> my.example.transport.zip, PKI.patch.txt
>
>
> When referencing a PKI enabled published WSDL via the Source URL I get the
> same exception as http://wso2.org/forum/thread/3377. From the research I've
> done and read it appears to do this because the Admin console is using the
> default KeyStore that comes with the JRE and it does a simple URLConnection.
> This thread talks to this issue: http://wso2.org/forum/thread/3621 and has
> sample code on a resolution.
> The key requirement would be to enable different KeyStores per WSDL reference.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Esb-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
