[
https://wso2.org/jira/browse/MASHUP-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18565#action_18565
]
Keith Godwin Chapman commented on MASHUP-1072:
----------------------------------------------
Fixed a bug related to this in revision 20521. Exceptions were not propagated
to the UI. The problenm you faced is this,
The certificate the Mashup Server ships with is a demo certificate which we've
created. Its not signed by a valid CS. Hence the public certificate cannot be
imported using this mechanism.
You can use a tool such as openssl to get the certificate in a scenario such as
this and then upload it using the UI. This is not straight and needs a couple
of steps to be done.
Shall I document this in the MS docs? But I feel that it will be better to
document this as a KB and point to that. Because this is something people will
need for other scenarios too.
> https access from one service to another.
> -----------------------------------------
>
> Key: MASHUP-1072
> URL: https://wso2.org/jira/browse/MASHUP-1072
> Project: WSO2 Mashup Server
> Issue Type: Bug
> Reporter: Jonathan Marsh
> Assignee: Keith Godwin Chapman
> Fix For: 1.5.1
>
> Attachments: jonathan-blogActivity.zip
>
>
> The enclosed service works fine when accessed from http (it tries to access
> itself and feedCache using the same protocol), but fails when accessed from
> https. I have uploaded a private key to my keystore, and even tried adding a
> cert for localhost. What am I doing wrong?
> Invoke the "fetchBlog" operation with the value
> "http://sanjiva.weerawarana.org/feeds/posts/default";.
> org.apache.axis2.AxisFault: org.wso2.mashup.MashupFault: Cannot recover
> key
> at
> org.wso2.javascript.rhino.JavaScriptEngine.call(JavaScriptEngine.java:184)
> at
> org.wso2.javascript.rhino.JavaScriptEngine.call(JavaScriptEngine.java:210)
> at
> org.wso2.javascript.rhino.JavaScriptReceiver.invokeBusinessLogic(JavaScriptReceiver.java:195)
> at
> org.apache.axis2.receivers.AbstractInOutMessageReceiver.invokeBusinessLogic(AbstractInOutMessageReceiver.java:40)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:100)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:176)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
> at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:131)
> at org.wso2.mashup.transport.MashupServlet.doPost(MashupServlet.java:69)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
--
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
_______________________________________________
Mashup-dev mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
