[ 
https://wso2.org/jira/browse/ESBJAVA-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruwan Linton resolved ESBJAVA-493.
----------------------------------

    Fix Version/s: 2.1
                       (was: FUTURE)
       Resolution: Fixed

should be fixed for the 2.1 release because the changes are already there in 
the synapse trunk

> 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: 2.1
>
>         Attachments: Enable ESB PKI Certificates.zip, ESBBuildFailError.txt, 
> 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]
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev

Reply via email to