Hi,
I have tested the scenarios for security use cases. I am getting the
following issue when test with the blocking and security. Blocking Sender
is not handled the security scenario properly.
[2015-03-05 12:42:36,601] ERROR {org.apache.axis2.engine.AxisEngine} -
Missing wsse:Security header in request
org.apache.axis2.AxisFault: Missing wsse:Security header in request
at
org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at
org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:459)
at
org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:277)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.rampart.RampartException: Missing wsse:Security
header in request
at org.apache.rampart.RampartEngine.process(RampartEngine.java:146)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
... 11 more
[2015-03-05 12:42:36,602] ERROR
{org.apache.synapse.transport.nhttp.ServerWorker} - Error processing POST
request
org.apache.axis2.AxisFault: Missing wsse:Security header in request
at
org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:180)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)
at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:261)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:167)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:172)
at
org.apache.synapse.transport.nhttp.ServerWorker.processEntityEnclosingMethod(ServerWorker.java:459)
at
org.apache.synapse.transport.nhttp.ServerWorker.run(ServerWorker.java:277)
at
org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.rampart.RampartException: Missing wsse:Security
header in request
at org.apache.rampart.RampartEngine.process(RampartEngine.java:146)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)
... 11 more
Thanks,
Kathees
On Wed, Mar 4, 2015 at 9:38 AM, Kathees Rajendram <kath...@wso2.com> wrote:
> Hi Isuru,
>
> Ok, I will test the scenarios for security use cases.
>
> Thanks,
> Kathees
>
> On Tue, Mar 3, 2015 at 8:57 PM, Isuru Udana <isu...@wso2.com> wrote:
>
>> Hi Kathees,
>>
>> Please include test scenarios for Security use cases as well.
>>
>> Thank you.
>>
>> On Tue, Mar 3, 2015 at 12:05 PM, Kathees Rajendram <kath...@wso2.com>
>> wrote:
>>
>>> Hi Isuru,
>>>
>>> I have tested the core functionality of blocking and non blocking.
>>> Please find the test plan and some test results.
>>>
>>>
>>>
>>> Test No
>>>
>>> Test
>>>
>>> Configuration
>>>
>>> Expected result
>>>
>>> Observed results
>>>
>>> Status
>>>
>>> Functional Testing
>>>
>>>
>>>
>>>
>>>
>>> 1
>>>
>>> Direct endpoint without blocking
>>>
>>>
>>> <call blocking=”false”><endpoint name="StockQuoteService">
>>>
>>> <address uri="
>>> http://localhost:9000/services/SimpleStockQuoteService";
>>> <http://localhost:9000/services/SimpleStockQuoteService>/>
>>>
>>> </endpoint>
>>>
>>> <call>
>>>
>>> Receive response
>>>
>>> Received response
>>>
>>> Passed
>>>
>>> 2
>>>
>>> Direct endpoint with blocking
>>>
>>> <call blocking=”true”><endpoint name="StockQuoteService">
>>>
>>> <address uri="
>>> http://localhost:9000/services/SimpleStockQuoteService";
>>> <http://localhost:9000/services/SimpleStockQuoteService>/>
>>>
>>> </endpoint>
>>>
>>> <call>
>>>
>>> Receive response
>>>
>>> Received response
>>>
>>> Passed
>>>
>>> 3
>>>
>>> Indirect endpoint without blocking
>>>
>>> <call blocking=”false”> <endpoint key="StockQuoteService"/>
>>>
>>> </call>
>>>
>>> Receive response
>>>
>>> Received response
>>>
>>> Passed
>>>
>>> 4
>>>
>>> Indirect endpoint with blocking
>>>
>>> <call blocking=”true”> <endpoint key="StockQuoteService"/>
>>>
>>> </call>
>>>
>>> Receive response
>>>
>>> Received response
>>>
>>> Passed
>>>
>>> 5
>>>
>>> Test blocking external service invocation during mediation.
>>>
>>>
>>>
>>> Pending
>>>
>>> 6
>>>
>>> Test non blocking when external service invocates during mediation.
>>>
>>>
>>>
>>> Pending
>>>
>>> 7
>>>
>>> Handle mutual SSL when blocking is true
>>>
>>> Add the following configuration to <ESB_HOME>/bin/wso2server.sh
>>>
>>> -Djavax.net.ssl.keyStore="$CARBON_HOME/repository/resources/security/wso2carbon.jks"
>>> \
>>>
>>> -Djavax.net.ssl.keyStorePassword="wso2carbon" \
>>>
>>> -Djavax.net.ssl.keyPassword="wso2carbon" \
>>>
>>>
>>> Pending
>>>
>>> 8
>>>
>>> Test with other endpoints
>>>
>>> - Address Endpoint
>>> - Default Endpoint
>>> - Failover Group
>>> - HTTP Endpoint
>>> - Load Balance Endpoint
>>> - Recipient List Group
>>> - Template Endpoint
>>> - WSDL Endpoint
>>>
>>> <call blocking=”false”> <endpoint key="StockQuoteService"/>
>>>
>>> </call>
>>>
>>>
>>>
>>>
>>> Pending
>>>
>>> UI Testing
>>>
>>>
>>>
>>>
>>>
>>> Pending
>>>
>>> 8
>>>
>>> Select None endpoint
>>>
>>>
>>>
>>> Pending
>>>
>>> 9
>>>
>>> Define the call mediator through the inline
>>>
>>>
>>>
>>> Pending
>>>
>>> 10
>>>
>>> Pick the endpoint path from the Registry
>>>
>>>
>>>
>>> Pending
>>>
>>> 11
>>>
>>> Specify the endpoint from Xpath
>>>
>>>
>>>
>>> Pending
>>>
>>> 12
>>>
>>> Add the configuration through the source view
>>>
>>>
>>>
>>> Pending
>>>
>>> 13
>>>
>>> Add the configuration through the design view
>>>
>>>
>>>
>>> Pending
>>>
>>> 12
>>>
>>> Switch to source view from design view
>>>
>>>
>>>
>>> Pending
>>>
>>> 13
>>>
>>> Switch to design view from source view
>>>
>>>
>>>
>>> Pending
>>>
>>> Thanks,
>>> Kathees
>>>
>>> On Tue, Mar 3, 2015 at 8:56 AM, Isuru Udana <isu...@wso2.com> wrote:
>>>
>>>> Hi Kathees,
>>>>
>>>> I believe you are conducting developer testing for newly implemented
>>>> functionality.
>>>> Could you please share the test plan with us.
>>>>
>>>> Thank you.
>>>>
>>>> On Fri, Feb 27, 2015 at 9:36 AM, Kathees Rajendram <kath...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Isuru,
>>>>>
>>>>> I will additionally add the following section for blocking
>>>>> functionality in call mediator.
>>>>>
>>>>>
>>>>>
>>>>> Thanks
>>>>> Kathees
>>>>>
>>>>>
>>>>> On Thu, Feb 26, 2015 at 10:48 AM, Kathees Rajendram <kath...@wso2.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Isuru,
>>>>>>
>>>>>> I have implemented the blocking functionality in call mediator.
>>>>>>
>>>>>> Please find the pull request [1] for wso2-synapse
>>>>>>
>>>>>> [1] - https://github.com/wso2/wso2-synapse/pull/93
>>>>>>
>>>>>> Thanks,
>>>>>> Kathees
>>>>>>
>>>>>> On Wed, Feb 25, 2015 at 5:06 PM, Kathees Rajendram <kath...@wso2.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Isuru,
>>>>>>>
>>>>>>> Endpoint with key is not handled in BlockingSender.I will introduce
>>>>>>> the changes in BlockingSender.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> kathees
>>>>>>>
>>>>>>> On Wed, Feb 25, 2015 at 4:26 PM, Isuru Udana <isu...@wso2.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi Kathees,
>>>>>>>>
>>>>>>>> If you find this not working, please introduce this change to the
>>>>>>>> BlockingMsgSender but not the Call Mediator. So that all the components
>>>>>>>> using BlockingMsgSender will inherit this.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Feb 25, 2015 at 4:14 PM, Isuru Udana <isu...@wso2.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi Kathees,
>>>>>>>>>
>>>>>>>>> On Tue, Feb 24, 2015 at 4:00 PM, Kathees Rajendram <
>>>>>>>>> kath...@wso2.com> wrote:
>>>>>>>>>
>>>>>>>>>> Hi Isuru,
>>>>>>>>>>
>>>>>>>>>> The blocking is working in the following synapse configuration.
>>>>>>>>>>
>>>>>>>>>> <call blocking="true">
>>>>>>>>>> <endpoint name="StockQuoteService">
>>>>>>>>>> <address uri="
>>>>>>>>>> http://localhost:9000/services/SimpleStockQuoteService"/>
>>>>>>>>>> </endpoint>
>>>>>>>>>> </call>
>>>>>>>>>>
>>>>>>>>>> but I want to add the blocking in the following configuration
>>>>>>>>>> also, as it is in call mediator.
>>>>>>>>>>
>>>>>>>>>> <call blocking="true">
>>>>>>>>>> <endpoint key="StockQuoteService"/>
>>>>>>>>>> </call>
>>>>>>>>>>
>>>>>>>>> I do not think you need to explicitly handle this. AFAIR
>>>>>>>>> BlockingMsgSender handles the IndirectEndpoint so no extra work
>>>>>>>>> needed.
>>>>>>>>>
>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> <endpoint name="StockQuoteService">
>>>>>>>>>> <address uri="
>>>>>>>>>> http://localhost:9000/services/SimpleStockQuoteService"/>
>>>>>>>>>> </endpoint>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Kathees
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, Feb 24, 2015 at 3:14 PM, Isuru Udana <isu...@wso2.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Kathees,
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, Feb 24, 2015 at 3:06 PM, Kathees Rajendram <
>>>>>>>>>>> kath...@wso2.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> The call mediator blocking is working with direct endpoint. I
>>>>>>>>>>>> want to write logic with endpoint key and Xpath. We can't use the
>>>>>>>>>>>> existing
>>>>>>>>>>>> functionality for blocking as it is in call mediator.
>>>>>>>>>>>>
>>>>>>>>>>> Could you please clarify what you mean by xpath here ?
>>>>>>>>>>> If you meant getting Source/Target xpath expressions in Callout
>>>>>>>>>>> mediator options into Call mediator, that is not required at all.
>>>>>>>>>>> Same for
>>>>>>>>>>> the endpoint key as well.
>>>>>>>>>>> Let's stick to the above discussed configuration syntax and
>>>>>>>>>>> functionality.
>>>>>>>>>>>
>>>>>>>>>>> Thanks.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Kathees
>>>>>>>>>>>> --
>>>>>>>>>>>> Kathees
>>>>>>>>>>>> Software Engineer,
>>>>>>>>>>>> email: kath...@wso2.com
>>>>>>>>>>>> mobile: +94772596173
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> *Isuru Udana*
>>>>>>>>>>> Senior
>>>>>>>>>>> *Software Engineer*
>>>>>>>>>>> WSO2 Inc.; http://wso2.com
>>>>>>>>>>> email: isu...@wso2.com cell: +94 77 3791887
>>>>>>>>>>> blog: http://mytecheye.blogspot.com/
>>>>>>>>>>> twitter: http://twitter.com/isudana
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Kathees
>>>>>>>>>> Software Engineer,
>>>>>>>>>> email: kath...@wso2.com
>>>>>>>>>> mobile: +94772596173
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Isuru Udana*
>>>>>>>>> Senior
>>>>>>>>> *Software Engineer*
>>>>>>>>> WSO2 Inc.; http://wso2.com
>>>>>>>>> email: isu...@wso2.com cell: +94 77 3791887
>>>>>>>>> blog: http://mytecheye.blogspot.com/
>>>>>>>>> twitter: http://twitter.com/isudana
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Isuru Udana*
>>>>>>>> Senior
>>>>>>>> *Software Engineer*
>>>>>>>> WSO2 Inc.; http://wso2.com
>>>>>>>> email: isu...@wso2.com cell: +94 77 3791887
>>>>>>>> blog: http://mytecheye.blogspot.com/
>>>>>>>> twitter: http://twitter.com/isudana
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Kathees
>>>>>>> Software Engineer,
>>>>>>> email: kath...@wso2.com
>>>>>>> mobile: +94772596173
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Kathees
>>>>>> Software Engineer,
>>>>>> email: kath...@wso2.com
>>>>>> mobile: +94772596173
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Kathees
>>>>> Software Engineer,
>>>>> email: kath...@wso2.com
>>>>> mobile: +94772596173
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Isuru Udana*
>>>> Senior
>>>> *Software Engineer*
>>>> WSO2 Inc.; http://wso2.com
>>>> email: isu...@wso2.com cell: +94 77 3791887
>>>> blog: http://mytecheye.blogspot.com/
>>>> twitter: http://twitter.com/isudana
>>>>
>>>
>>>
>>>
>>> --
>>> Kathees
>>> Software Engineer,
>>> email: kath...@wso2.com
>>> mobile: +94772596173
>>>
>>
>>
>>
>> --
>> *Isuru Udana*
>> Senior
>> *Software Engineer*
>> WSO2 Inc.; http://wso2.com
>> email: isu...@wso2.com cell: +94 77 3791887
>> blog: http://mytecheye.blogspot.com/
>> twitter: http://twitter.com/isudana
>>
>
>
>
> --
> Kathees
> Software Engineer,
> email: kath...@wso2.com
> mobile: +94772596173
>
--
Kathees
Software Engineer,
email: kath...@wso2.com
mobile: +94772596173
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
