[Dev] Version format change in Axis2 root pom and Orbit pom

[Malaka Gangananda]

Hi All,

In axis2 release versions prior to 1.6.1-wso2v23 in the root pom the
version is given as 1.6.1-wso2v22 but in orbit axis2 pom the version is
given as 1.6.1.wso2v22(with a dot).
Any reason for this?
Also after releasing from the jenkins (release 1.6.1-wso2v23) in the orbit
axis2 pom the version is also given as 1.6.1-wso2v23(with a “-” )
Could this be leading to any issues?


Thanks,
-- 
Malaka.
-- 
Malaka Gangananda - Software Engineer | WSO2
Email : mala...@wso2.com
Mobile : +94713564340
Web : http://wso2.com
  
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Bug # IDENTITY-7317

[Ruwan Abeykoon]

Hi Pooja,
We strive to maintain backward compatibility as much as possible. But we
also improve on defects and spec violations, which may not be backward
compatible.

Could you please explain which version it "worked" for you and which
version you tested which causes the incompatibility.

Cheers,
Ruwan


On Wed, Feb 7, 2018 at 12:56 PM, Pooja Gupta 
wrote:

> Thanks for responding.
>
>
>
> In the older version of WOS2 implementation it was just checking for 302 /
> 200 and was not validating response received. But in 5.0.4 apart from
> checking 200/302 it does validate the response [highlighted red below –
> LogoutRequestSender.class] and that too only POST and that redirects are
> not handled.
>
>
>
> Because of this the code at our end is breaking. Looks like backward
> compatibility is not provided.
>
>
>
>
>
> Shall I log issue on this??
>
>
>
>
>
>
>
> *From:* Chiran Wijesekara [mailto:chir...@wso2.com]
> *Sent:* 07 February 2018 09:04
> *To:* Ruwan Abeykoon 
> *Cc:* Pooja Gupta ; Deepak Singla <
> deepak.sin...@edifecs.com>; dev@wso2.org
> *Subject:* Re: [Dev] Bug # IDENTITY-7317
>
>
>
> Hi,
>
> AFAIK, the current implementation of SAML *Single Logout* in wso2 Identity
> Server is only done for back channel mode( i.e. without browser involvement
> and no redirections). Currently IS *does not support* redirect based
> front channel mechanism.
>
> In the back-channel mode, at the Identity Server side, it checks just for
> 200 OK from session participating other SPs.
>
> Thanks
>
>
>
> On Tue, Feb 6, 2018 at 2:41 PM, Ruwan Abeykoon  wrote:
>
> Hi Deepak/Pooja,
>
> Thanks for the detailed report on IDENTITY-7317. We will certainly go
> through this and provide you the update ASAP.
>
>
>
> Cheers,
>
> Ruwan
>
>
>
> On Tue, Feb 6, 2018 at 2:09 PM, Pooja Gupta 
> wrote:
>
> + Deepak
>
>
>
> *From:* Pooja Gupta
> *Sent:* 06 February 2018 14:09
> *To:* 'dev@wso2.org' ; 'ruw...@wso2.com' 
> *Subject:* Bug # IDENTITY-7317
>
>
>
> Hello,
>
>
>
> I have raised a defect on WSO2 IDP. IDP not handling redirect logout
> response sent from SP to IDP when SP receives unsolicited logout request
> from IDP.
>
>
>
> Appreciate if you could look into the issue. We can talk more for more
> details.
>
>
>
> https://wso2.org/jira/browse/IDENTITY-7317
>
>
>
> Thanks
>
> Pooja
>
>
>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
>
>
> --
>
> *Chiran Wijesekara*
>
>
> *Software Engineering Intern | WSO2 *Email: chir...@wso2.com
> Mobile: +94712990173web: www.wso2.com
>
> [image: https://wso2.com/signature] 
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Fwd: [DEV] Please review and merge PR

[Chanaka Cooray]

Hi,

Merged the PR.

Thanks,
Chanaka.

On Sun, Feb 4, 2018 at 9:28 PM, 김대경  wrote:

> Why it doesn't merged.. although approved.
>
>
> -- 전달된 메일 --
> 보낸사람: "김대경" 
> 날짜: 2018. 1. 30. 오전 11:03
> 제목: [DEV] Please review and merge PR
> 받는사람: 
> 참조:
>
> Can you please review and merge PR.
>
> [1] https://github.com/wso2/wso2-axis2/pull/132
>
> Best Regards.
> Daekyung Kim.
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Chanaka Cooray
Software Engineer, WSO2 Inc. http://wso2.com
Email: chana...@wso2.com
Mobile: +94713149860

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] wso2 http access logs customization

[Chiran Wijesekara]

Hi,
What is the error you get once you try to run the wso2server.bat file in
your windows environment?. Would be glad if you can paste the error log.
Thanks

On Wed, Feb 7, 2018 at 10:52 AM, Deepak Singla 
wrote:

> Any update please.
>
>
>
>
>
> *From:* Prakhash Sivakumar [mailto:prakh...@wso2.com ]
> *Sent:* Tuesday, January 16, 2018 12:58 PM
> *To:* Deepak Singla 
> *Cc:* WSO2 Developers' List 
> *Subject:* Re: wso2 http access logs customization
>
>
>
> Hi Deepak,
>
>
>
> Moving this discussion to the DEV as this is not about a security issue.
>
>
>
> Thanks,
>
> Prakhash
>
>
>
> On Tue, Jan 16, 2018 at 12:54 PM, Deepak Singla 
> wrote:
>
> Hello Wso2 Team
>
>
>
> I configured wso2 5.4.0 Identity Service on window environment. Here I am
> trying to customizing the maximum file size and Maximun back up index of
> http_access*.log, then I followed this link
> 
> to customize http_access logs.
>
>
>
> I also found this file *logging-bridge.properties* under directory
> “wso2\repository\conf\etc\logging-bridge.properties”. I applied above
> changes mentioned in link in logging-bridge.properties file. Like
>
> # Define the FileHandler
>
> handlers= java.util.logging.FileHandler
>
>
>
> # Configure the FileHandler
>
> java.util.logging.FileHandler.pattern = %h/java%u.log
>
> java.util.logging.FileHandler.limit = 1024000
>
> java.util.logging.FileHandler.count = 3
>
> java.util.logging.FileHandler.formatter =  java.util.logging.SimpleFormat
> ter
>
> java.util.logging.FileHandler.append=true
>
>
>
> Then I restarted the wso2 server, but it is not working for me.
>
>
>
> Kindly provide me your inputs to resolve this issue.
>
>
>
> Regards
>
> Deepak
>
>
>
>
>
> --
>
> Prakhash Sivakumar
>
> Software Engineer | WSO2 Inc
>
> Platform Security Team
>
> Mobile : +94771510080 <+94%2077%20151%200080>
>
> Blog : https://medium.com/@PrakhashS
>



-- 
*Chiran Wijesekara*


*Software Engineering Intern | WSO2*Email: chir...@wso2.com
Mobile: +94712990173web: www.wso2.com

[image: https://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Posting a plain text message to queue

[dhanya]

Hi,

Anyone has information on how this can be done?

Thanks and regards
Dhanya



--
Sent from: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Development-f3.html
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Unnecessary debug logs in org.apache.synapse.mediators.builtin.LogMediator

[Senduran Balasubramaniyam]

Hi Godwin,

>
>  Do you see any advantage/value by adding those logs?
>
Its depends on the context, say we have a large mediation and if we are
having an issue, at such instances these logs may help to pinpoint the
issue, specially when there are nested mediators. the "Start" and "End"
 logs are common for all the synapse mediators and it should not be seen in
the mediation logs. Anyway kindly let us know if you are still facing the
issue of having these logs

>
> Thanks
> Godwin
>
> On Wed, Feb 7, 2018 at 9:56 AM, Senduran Balasubramaniyam <
> sendu...@wso2.com> wrote:
>
>> Hi Godwin,
>>
>> These are internal logs for debugging the synapse code. when there are
>> lot of mediators this will be helpful. If you getting this log in your log
>> mediator logs. you may need to revisit your log4j properties because when a
>> log mediator category is set to debug you should not see this log
>>
>> Regards
>> Senduran
>>
>> On Wed, Feb 7, 2018 at 9:51 AM, Godwin Shrimal  wrote:
>>
>>> Hi Integration Team,
>>>
>>> Any feedback on this?
>>>
>>> Thanks
>>> Godwin
>>>
>>> On Fri, Jan 19, 2018 at 5:52 PM, Godwin Shrimal  wrote:
>>>
 Hi Devs,

 Shall we remove "End : Log mediator" and "End : Log mediator" debug
 logs in [1] and [2]? I don't see any value with those debug logs and it's
 annoying when we enable debug logs for 
 "org.apache.synapse.mediators.builtin.LogMediator"
 in dev environments.

 [1] https://github.com/wso2/wso2-synapse/blob/master/modules/cor
 e/src/main/java/org/apache/synapse/mediators/builtin/LogMedi
 ator.java#L92
 [2] https://github.com/wso2/wso2-synapse/blob/master/modules/cor
 e/src/main/java/org/apache/synapse/mediators/builtin/LogMedi
 ator.java#L124

 Thanks
 Godwin

 --
 *Godwin Amila Shrimal*
 Associate Technical Lead
 WSO2 Inc.; http://wso2.com
 lean.enterprise.middleware

 mobile: *+94772264165*
 linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
 *
 twitter: https://twitter.com/godwinamila
 

>>>
>>>
>>>
>>> --
>>> *Godwin Amila Shrimal*
>>> Associate Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94772264165*
>>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
>>> *
>>> twitter: https://twitter.com/godwinamila
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Senduran *
>> Senior Software Engineer,
>> WSO2, Inc.;  http://wso2.com/ 
>> Mobile: +94 77 952 6548 <+94%2077%20952%206548>
>>
>
>
>
> --
> *Godwin Amila Shrimal*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
> *
> twitter: https://twitter.com/godwinamila
> 
>



-- 
*Senduran *
Senior Software Engineer,
WSO2, Inc.;  http://wso2.com/ 
Mobile: +94 77 952 6548 <+94%2077%20952%206548>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Unnecessary debug logs in org.apache.synapse.mediators.builtin.LogMediator

[Godwin Shrimal]

Hi Senduran,

Thanks for your feedback. I am getting these logs when I change
org.apache.synapse.mediators.builtin.LogMediator to DEBUG. I am trying with
the fresh pack without changing any configuration in log4j.properties. Then
there should be something wrong with default log4j.properties file pack
with the product. But I doubt debug log I mentioned above has any value. Do
you see any advantage/value by adding those logs?

Thanks
Godwin

On Wed, Feb 7, 2018 at 9:56 AM, Senduran Balasubramaniyam  wrote:

> Hi Godwin,
>
> These are internal logs for debugging the synapse code. when there are lot
> of mediators this will be helpful. If you getting this log in your log
> mediator logs. you may need to revisit your log4j properties because when a
> log mediator category is set to debug you should not see this log
>
> Regards
> Senduran
>
> On Wed, Feb 7, 2018 at 9:51 AM, Godwin Shrimal  wrote:
>
>> Hi Integration Team,
>>
>> Any feedback on this?
>>
>> Thanks
>> Godwin
>>
>> On Fri, Jan 19, 2018 at 5:52 PM, Godwin Shrimal  wrote:
>>
>>> Hi Devs,
>>>
>>> Shall we remove "End : Log mediator" and "End : Log mediator" debug
>>> logs in [1] and [2]? I don't see any value with those debug logs and it's
>>> annoying when we enable debug logs for 
>>> "org.apache.synapse.mediators.builtin.LogMediator"
>>> in dev environments.
>>>
>>> [1] https://github.com/wso2/wso2-synapse/blob/master/modules/cor
>>> e/src/main/java/org/apache/synapse/mediators/builtin/LogMedi
>>> ator.java#L92
>>> [2] https://github.com/wso2/wso2-synapse/blob/master/modules/cor
>>> e/src/main/java/org/apache/synapse/mediators/builtin/LogMedi
>>> ator.java#L124
>>>
>>> Thanks
>>> Godwin
>>>
>>> --
>>> *Godwin Amila Shrimal*
>>> Associate Technical Lead
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94772264165*
>>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
>>> *
>>> twitter: https://twitter.com/godwinamila
>>> 
>>>
>>
>>
>>
>> --
>> *Godwin Amila Shrimal*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
>> *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Senduran *
> Senior Software Engineer,
> WSO2, Inc.;  http://wso2.com/ 
> Mobile: +94 77 952 6548 <+94%2077%20952%206548>
>



-- 
*Godwin Amila Shrimal*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94772264165*
linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
*
twitter: https://twitter.com/godwinamila

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Unnecessary debug logs in org.apache.synapse.mediators.builtin.LogMediator

[Senduran Balasubramaniyam]

Hi Godwin,

These are internal logs for debugging the synapse code. when there are lot
of mediators this will be helpful. If you getting this log in your log
mediator logs. you may need to revisit your log4j properties because when a
log mediator category is set to debug you should not see this log

Regards
Senduran

On Wed, Feb 7, 2018 at 9:51 AM, Godwin Shrimal  wrote:

> Hi Integration Team,
>
> Any feedback on this?
>
> Thanks
> Godwin
>
> On Fri, Jan 19, 2018 at 5:52 PM, Godwin Shrimal  wrote:
>
>> Hi Devs,
>>
>> Shall we remove "End : Log mediator" and "End : Log mediator" debug logs
>> in [1] and [2]? I don't see any value with those debug logs and it's
>> annoying when we enable debug logs for 
>> "org.apache.synapse.mediators.builtin.LogMediator"
>> in dev environments.
>>
>> [1] https://github.com/wso2/wso2-synapse/blob/master/modules/cor
>> e/src/main/java/org/apache/synapse/mediators/builtin/LogMediator.java#L92
>> [2] https://github.com/wso2/wso2-synapse/blob/master/modules/cor
>> e/src/main/java/org/apache/synapse/mediators/builtin/LogMedi
>> ator.java#L124
>>
>> Thanks
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> Associate Technical Lead
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
>> *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>
>
>
> --
> *Godwin Amila Shrimal*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
> *
> twitter: https://twitter.com/godwinamila
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Senduran *
Senior Software Engineer,
WSO2, Inc.;  http://wso2.com/ 
Mobile: +94 77 952 6548
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Unnecessary debug logs in org.apache.synapse.mediators.builtin.LogMediator

[Godwin Shrimal]

Hi Integration Team,

Any feedback on this?

Thanks
Godwin

On Fri, Jan 19, 2018 at 5:52 PM, Godwin Shrimal  wrote:

> Hi Devs,
>
> Shall we remove "End : Log mediator" and "End : Log mediator" debug logs
> in [1] and [2]? I don't see any value with those debug logs and it's
> annoying when we enable debug logs for 
> "org.apache.synapse.mediators.builtin.LogMediator"
> in dev environments.
>
> [1] https://github.com/wso2/wso2-synapse/blob/master/modules/
> core/src/main/java/org/apache/synapse/mediators/builtin/
> LogMediator.java#L92
> [2] https://github.com/wso2/wso2-synapse/blob/master/modules/
> core/src/main/java/org/apache/synapse/mediators/builtin/
> LogMediator.java#L124
>
> Thanks
> Godwin
>
> --
> *Godwin Amila Shrimal*
> Associate Technical Lead
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
> *
> twitter: https://twitter.com/godwinamila
> 
>



-- 
*Godwin Amila Shrimal*
Associate Technical Lead
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: *+94772264165*
linkedin: *https://www.linkedin.com/in/godwin-amila-2ba26844/
*
twitter: https://twitter.com/godwinamila

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Bug # IDENTITY-7317

[Chiran Wijesekara]

Hi,
AFAIK, the current implementation of SAML *Single Logout* in wso2 Identity
Server is only done for back channel mode( i.e. without browser involvement
and no redirections). Currently IS *does not support* redirect based front
channel mechanism.
In the back-channel mode, at the Identity Server side, it checks just for
200 OK from session participating other SPs.
Thanks

On Tue, Feb 6, 2018 at 2:41 PM, Ruwan Abeykoon  wrote:

> Hi Deepak/Pooja,
> Thanks for the detailed report on IDENTITY-7317. We will certainly go
> through this and provide you the update ASAP.
>
> Cheers,
> Ruwan
>
> On Tue, Feb 6, 2018 at 2:09 PM, Pooja Gupta 
> wrote:
>
>> + Deepak
>>
>>
>>
>> *From:* Pooja Gupta
>> *Sent:* 06 February 2018 14:09
>> *To:* 'dev@wso2.org' ; 'ruw...@wso2.com' 
>> *Subject:* Bug # IDENTITY-7317
>>
>>
>>
>> Hello,
>>
>>
>>
>> I have raised a defect on WSO2 IDP. IDP not handling redirect logout
>> response sent from SP to IDP when SP receives unsolicited logout request
>> from IDP.
>>
>>
>>
>> Appreciate if you could look into the issue. We can talk more for more
>> details.
>>
>>
>>
>> https://wso2.org/jira/browse/IDENTITY-7317
>>
>>
>>
>> Thanks
>>
>> Pooja
>>
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Chiran Wijesekara*


*Software Engineering Intern | WSO2*Email: chir...@wso2.com
Mobile: +94712990173web: www.wso2.com

[image: https://wso2.com/signature] 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Please review and merge PR

[Nishadi Kirielle]

Hi Kim,

Thank you for your contribution. We are reviewing your PR.
As we are trying to reproduce the issue, can you please provide the exact
scenario where you faced this issue?

Thank you and regards,
Nishadi

On Sun, Feb 4, 2018 at 9:31 PM, 김대경  wrote:

>
> I wonder how it is progressing...
>
>
>
> 2018. 1. 26. 오후 1:31에 "김대경" 님이 작성:
>
> Can you please review and merge PR[1] .
>
> [1] https://github.com/wso2/wso2-commons-httpclient/pull/18
>
> Best Regards.
> Daekyung Kim.
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Nishadi Kirielle*
Software Engineer
WSO2, Inc.

Mobile : +94 70 204 5934
Blog : nishadikirielle.wordpress.com


___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error code unsupported_client_authentication_method in IS-5.4.1

[Nilasini Thirunavukkarasu]

Hi,

Thanks. Sent the PR.

Thanks,
Nila.

On Wed, Feb 7, 2018 at 12:00 AM, Hasintha Indrajee 
wrote:

>
>
> On Tue, Feb 6, 2018 at 11:43 PM, Nilasini Thirunavukkarasu <
> nilas...@wso2.com> wrote:
>
>> Hi,
>>
>> Thank you for the reply.
>>
>> I have checked it in identity-inbound-auth-oauth 5.6.x branch which is
>> used for 5.5.0, the error code was changed from 
>> *unsupported_client_authentication_method
>> *but anyhow it has been changed to *invalid_request.*Shouldn't we
>> need to change the error code as *invalid_client*?
>>
>
> +1. Let's do this change.
>
>>
>> [1] https://github.com/wso2-extensions/identity-inbound-auth
>> -oauth/blob/5.6.x/components/org.wso2.carbon.identity.
>> oauth/src/main/java/org/wso2/carbon/identity/oauth2/token/A
>> ccessTokenIssuer.java#L168-L170
>>
>>
>> Thanks,
>> Nila.
>>
>> On Tue, Feb 6, 2018 at 10:49 PM, Hasintha Indrajee 
>> wrote:
>>
>>>
>>>
>>> On Tue, Feb 6, 2018 at 10:32 PM, Maduranga Siriwardena <
>>> madura...@wso2.com> wrote:
>>>
 Hi Nilasini,

 Yes, unsupported_client_authentication_method is a incorrect error
 message. So we need to fix this.

 I think this should be already fixed in IS 5.5.0 branch. *@Hasintha*,
 can you confirm?

>>>
>>> IIRC this is already fixed in 5.5.0-snapshot
>>>

 Thanks,

 On Tue, Feb 6, 2018 at 5:07 PM, Nilasini Thirunavukkarasu <
 nilas...@wso2.com> wrote:

> Hi,
>
> In IS-5.4.1 if there is no client authentication in the token request,
> we are giving the error code
> *unsupported_client_authentication_method*. According to the spec[1],
> if there is no client authentication or unsupported client authentication,
> it will fall under "invalid_client".
>
> invalid_client
>Client authentication failed (e.g., unknown client, no
>client authentication included, or unsupported
>authentication method).  The authorization server MAY
>return an HTTP 401 (Unauthorized) status code to indicate
>which HTTP authentication schemes are supported.  If the
>client attempted to authenticate via the "Authorization"
>request header field, the authorization server MUST
>respond with an HTTP 401 (Unauthorized) status code and
>include the "WWW-Authenticate" response header field
>matching the authentication scheme used by the client.
>
>
>
>
> According to the spec, there is no standard error code like 
> *unsupported_client_authentication_method.
> *Is there any specific reason to introduce a new error code
> *unsupported_client_authentication_method *in IS5.4.1?.
>
> Example:-
>
> request:-
> curl -H  -k -d "grant_type=client_credentials" -H
> "Content-Type:application/x-www-form-urlencoded"
> https://localhost:9443/oauth2/token -k
>
> response:-
> {"error_description":"Unsupported Client Authentication
> Method!","error":"unsupported_client_authentication_method"}
>
> Please correct me if I'm wrong.
>
> [1] https://tools.ietf.org/html/rfc6749#section-5.2
>
>
> Thanks,
> Nila.
>
> --
> Nilasini Thirunavukkarasu
> Software Engineer - WSO2
>
> Email : nilas...@wso2.com
> Mobile : +94775241823 <+94%2077%20524%201823>
> Web : http://wso2.com/
>
>
> 
>



 --
 Maduranga Siriwardena
 Senior Software Engineer
 WSO2 Inc; http://wso2.com/

 Email: madura...@wso2.com
 Mobile: +94718990591 <071%20899%200591>
 Blog: *https://madurangasiriwardena.wordpress.com/
 *
 

>>>
>>>
>>>
>>> --
>>> Hasintha Indrajee
>>> WSO2, Inc.
>>> Mobile:+94 771892453 <+94%2077%20189%202453>
>>>
>>>
>>
>>
>> --
>> Nilasini Thirunavukkarasu
>> Software Engineer - WSO2
>>
>> Email : nilas...@wso2.com
>> Mobile : +94775241823 <077%20524%201823>
>> Web : http://wso2.com/
>>
>>
>> 
>>
>
>
>
> --
> Hasintha Indrajee
> WSO2, Inc.
> Mobile:+94 771892453 <+94%2077%20189%202453>
>
>


-- 
Nilasini Thirunavukkarasu
Software Engineer - WSO2

Email : nilas...@wso2.com
Mobile : +94775241823
Web : http://wso2.com/



___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error code unsupported_client_authentication_method in IS-5.4.1

[Hasintha Indrajee]

On Tue, Feb 6, 2018 at 11:43 PM, Nilasini Thirunavukkarasu <
nilas...@wso2.com> wrote:

> Hi,
>
> Thank you for the reply.
>
> I have checked it in identity-inbound-auth-oauth 5.6.x branch which is
> used for 5.5.0, the error code was changed from 
> *unsupported_client_authentication_method
> *but anyhow it has been changed to *invalid_request.*Shouldn't we need to
> change the error code as *invalid_client*?
>

+1. Let's do this change.

>
> [1] https://github.com/wso2-extensions/identity-inbound-
> auth-oauth/blob/5.6.x/components/org.wso2.carbon.
> identity.oauth/src/main/java/org/wso2/carbon/identity/oauth2/token/
> AccessTokenIssuer.java#L168-L170
>
>
> Thanks,
> Nila.
>
> On Tue, Feb 6, 2018 at 10:49 PM, Hasintha Indrajee 
> wrote:
>
>>
>>
>> On Tue, Feb 6, 2018 at 10:32 PM, Maduranga Siriwardena <
>> madura...@wso2.com> wrote:
>>
>>> Hi Nilasini,
>>>
>>> Yes, unsupported_client_authentication_method is a incorrect error
>>> message. So we need to fix this.
>>>
>>> I think this should be already fixed in IS 5.5.0 branch. *@Hasintha*,
>>> can you confirm?
>>>
>>
>> IIRC this is already fixed in 5.5.0-snapshot
>>
>>>
>>> Thanks,
>>>
>>> On Tue, Feb 6, 2018 at 5:07 PM, Nilasini Thirunavukkarasu <
>>> nilas...@wso2.com> wrote:
>>>
 Hi,

 In IS-5.4.1 if there is no client authentication in the token request,
 we are giving the error code *unsupported_client_authentication_method*.
 According to the spec[1], if there is no client authentication or
 unsupported client authentication, it will fall under "invalid_client".

 invalid_client
Client authentication failed (e.g., unknown client, no
client authentication included, or unsupported
authentication method).  The authorization server MAY
return an HTTP 401 (Unauthorized) status code to indicate
which HTTP authentication schemes are supported.  If the
client attempted to authenticate via the "Authorization"
request header field, the authorization server MUST
respond with an HTTP 401 (Unauthorized) status code and
include the "WWW-Authenticate" response header field
matching the authentication scheme used by the client.




 According to the spec, there is no standard error code like 
 *unsupported_client_authentication_method.
 *Is there any specific reason to introduce a new error code
 *unsupported_client_authentication_method *in IS5.4.1?.

 Example:-

 request:-
 curl -H  -k -d "grant_type=client_credentials" -H
 "Content-Type:application/x-www-form-urlencoded"
 https://localhost:9443/oauth2/token -k

 response:-
 {"error_description":"Unsupported Client Authentication
 Method!","error":"unsupported_client_authentication_method"}

 Please correct me if I'm wrong.

 [1] https://tools.ietf.org/html/rfc6749#section-5.2


 Thanks,
 Nila.

 --
 Nilasini Thirunavukkarasu
 Software Engineer - WSO2

 Email : nilas...@wso2.com
 Mobile : +94775241823 <+94%2077%20524%201823>
 Web : http://wso2.com/


 

>>>
>>>
>>>
>>> --
>>> Maduranga Siriwardena
>>> Senior Software Engineer
>>> WSO2 Inc; http://wso2.com/
>>>
>>> Email: madura...@wso2.com
>>> Mobile: +94718990591 <071%20899%200591>
>>> Blog: *https://madurangasiriwardena.wordpress.com/
>>> *
>>> 
>>>
>>
>>
>>
>> --
>> Hasintha Indrajee
>> WSO2, Inc.
>> Mobile:+94 771892453 <+94%2077%20189%202453>
>>
>>
>
>
> --
> Nilasini Thirunavukkarasu
> Software Engineer - WSO2
>
> Email : nilas...@wso2.com
> Mobile : +94775241823 <077%20524%201823>
> Web : http://wso2.com/
>
>
> 
>



-- 
Hasintha Indrajee
WSO2, Inc.
Mobile:+94 771892453
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error code unsupported_client_authentication_method in IS-5.4.1

[Nilasini Thirunavukkarasu]

Hi,

Thank you for the reply.

I have checked it in identity-inbound-auth-oauth 5.6.x branch which is used
for 5.5.0, the error code was changed from
*unsupported_client_authentication_method
*but anyhow it has been changed to *invalid_request.*Shouldn't we need to
change the error code as *invalid_client*?

[1]
https://github.com/wso2-extensions/identity-inbound-auth-oauth/blob/5.6.x/components/org.wso2.carbon.identity.oauth/src/main/java/org/wso2/carbon/identity/oauth2/token/AccessTokenIssuer.java#L168-L170


Thanks,
Nila.

On Tue, Feb 6, 2018 at 10:49 PM, Hasintha Indrajee 
wrote:

>
>
> On Tue, Feb 6, 2018 at 10:32 PM, Maduranga Siriwardena  > wrote:
>
>> Hi Nilasini,
>>
>> Yes, unsupported_client_authentication_method is a incorrect error
>> message. So we need to fix this.
>>
>> I think this should be already fixed in IS 5.5.0 branch. *@Hasintha*,
>> can you confirm?
>>
>
> IIRC this is already fixed in 5.5.0-snapshot
>
>>
>> Thanks,
>>
>> On Tue, Feb 6, 2018 at 5:07 PM, Nilasini Thirunavukkarasu <
>> nilas...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> In IS-5.4.1 if there is no client authentication in the token request,
>>> we are giving the error code *unsupported_client_authentication_method*.
>>> According to the spec[1], if there is no client authentication or
>>> unsupported client authentication, it will fall under "invalid_client".
>>>
>>> invalid_client
>>>Client authentication failed (e.g., unknown client, no
>>>client authentication included, or unsupported
>>>authentication method).  The authorization server MAY
>>>return an HTTP 401 (Unauthorized) status code to indicate
>>>which HTTP authentication schemes are supported.  If the
>>>client attempted to authenticate via the "Authorization"
>>>request header field, the authorization server MUST
>>>respond with an HTTP 401 (Unauthorized) status code and
>>>include the "WWW-Authenticate" response header field
>>>matching the authentication scheme used by the client.
>>>
>>>
>>>
>>>
>>> According to the spec, there is no standard error code like 
>>> *unsupported_client_authentication_method.
>>> *Is there any specific reason to introduce a new error code
>>> *unsupported_client_authentication_method *in IS5.4.1?.
>>>
>>> Example:-
>>>
>>> request:-
>>> curl -H  -k -d "grant_type=client_credentials" -H
>>> "Content-Type:application/x-www-form-urlencoded"
>>> https://localhost:9443/oauth2/token -k
>>>
>>> response:-
>>> {"error_description":"Unsupported Client Authentication
>>> Method!","error":"unsupported_client_authentication_method"}
>>>
>>> Please correct me if I'm wrong.
>>>
>>> [1] https://tools.ietf.org/html/rfc6749#section-5.2
>>>
>>>
>>> Thanks,
>>> Nila.
>>>
>>> --
>>> Nilasini Thirunavukkarasu
>>> Software Engineer - WSO2
>>>
>>> Email : nilas...@wso2.com
>>> Mobile : +94775241823 <+94%2077%20524%201823>
>>> Web : http://wso2.com/
>>>
>>>
>>> 
>>>
>>
>>
>>
>> --
>> Maduranga Siriwardena
>> Senior Software Engineer
>> WSO2 Inc; http://wso2.com/
>>
>> Email: madura...@wso2.com
>> Mobile: +94718990591 <071%20899%200591>
>> Blog: *https://madurangasiriwardena.wordpress.com/
>> *
>> 
>>
>
>
>
> --
> Hasintha Indrajee
> WSO2, Inc.
> Mobile:+94 771892453 <+94%2077%20189%202453>
>
>


-- 
Nilasini Thirunavukkarasu
Software Engineer - WSO2

Email : nilas...@wso2.com
Mobile : +94775241823
Web : http://wso2.com/



___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error code unsupported_client_authentication_method in IS-5.4.1

[Hasintha Indrajee]

On Tue, Feb 6, 2018 at 10:32 PM, Maduranga Siriwardena 
wrote:

> Hi Nilasini,
>
> Yes, unsupported_client_authentication_method is a incorrect error
> message. So we need to fix this.
>
> I think this should be already fixed in IS 5.5.0 branch. *@Hasintha*, can
> you confirm?
>

IIRC this is already fixed in 5.5.0-snapshot

>
> Thanks,
>
> On Tue, Feb 6, 2018 at 5:07 PM, Nilasini Thirunavukkarasu <
> nilas...@wso2.com> wrote:
>
>> Hi,
>>
>> In IS-5.4.1 if there is no client authentication in the token request, we
>> are giving the error code *unsupported_client_authentication_method*.
>> According to the spec[1], if there is no client authentication or
>> unsupported client authentication, it will fall under "invalid_client".
>>
>> invalid_client
>>Client authentication failed (e.g., unknown client, no
>>client authentication included, or unsupported
>>authentication method).  The authorization server MAY
>>return an HTTP 401 (Unauthorized) status code to indicate
>>which HTTP authentication schemes are supported.  If the
>>client attempted to authenticate via the "Authorization"
>>request header field, the authorization server MUST
>>respond with an HTTP 401 (Unauthorized) status code and
>>include the "WWW-Authenticate" response header field
>>matching the authentication scheme used by the client.
>>
>>
>>
>>
>> According to the spec, there is no standard error code like 
>> *unsupported_client_authentication_method.
>> *Is there any specific reason to introduce a new error code
>> *unsupported_client_authentication_method *in IS5.4.1?.
>>
>> Example:-
>>
>> request:-
>> curl -H  -k -d "grant_type=client_credentials" -H
>> "Content-Type:application/x-www-form-urlencoded"
>> https://localhost:9443/oauth2/token -k
>>
>> response:-
>> {"error_description":"Unsupported Client Authentication
>> Method!","error":"unsupported_client_authentication_method"}
>>
>> Please correct me if I'm wrong.
>>
>> [1] https://tools.ietf.org/html/rfc6749#section-5.2
>>
>>
>> Thanks,
>> Nila.
>>
>> --
>> Nilasini Thirunavukkarasu
>> Software Engineer - WSO2
>>
>> Email : nilas...@wso2.com
>> Mobile : +94775241823 <+94%2077%20524%201823>
>> Web : http://wso2.com/
>>
>>
>> 
>>
>
>
>
> --
> Maduranga Siriwardena
> Senior Software Engineer
> WSO2 Inc; http://wso2.com/
>
> Email: madura...@wso2.com
> Mobile: +94718990591 <071%20899%200591>
> Blog: *https://madurangasiriwardena.wordpress.com/
> *
> 
>



-- 
Hasintha Indrajee
WSO2, Inc.
Mobile:+94 771892453
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Error code unsupported_client_authentication_method in IS-5.4.1

[Maduranga Siriwardena]

Hi Nilasini,

Yes, unsupported_client_authentication_method is a incorrect error message.
So we need to fix this.

I think this should be already fixed in IS 5.5.0 branch. *@Hasintha*, can
you confirm?

Thanks,

On Tue, Feb 6, 2018 at 5:07 PM, Nilasini Thirunavukkarasu  wrote:

> Hi,
>
> In IS-5.4.1 if there is no client authentication in the token request, we
> are giving the error code *unsupported_client_authentication_method*.
> According to the spec[1], if there is no client authentication or
> unsupported client authentication, it will fall under "invalid_client".
>
> invalid_client
>Client authentication failed (e.g., unknown client, no
>client authentication included, or unsupported
>authentication method).  The authorization server MAY
>return an HTTP 401 (Unauthorized) status code to indicate
>which HTTP authentication schemes are supported.  If the
>client attempted to authenticate via the "Authorization"
>request header field, the authorization server MUST
>respond with an HTTP 401 (Unauthorized) status code and
>include the "WWW-Authenticate" response header field
>matching the authentication scheme used by the client.
>
>
>
>
> According to the spec, there is no standard error code like 
> *unsupported_client_authentication_method.
> *Is there any specific reason to introduce a new error code
> *unsupported_client_authentication_method *in IS5.4.1?.
>
> Example:-
>
> request:-
> curl -H  -k -d "grant_type=client_credentials" -H
> "Content-Type:application/x-www-form-urlencoded"
> https://localhost:9443/oauth2/token -k
>
> response:-
> {"error_description":"Unsupported Client Authentication
> Method!","error":"unsupported_client_authentication_method"}
>
> Please correct me if I'm wrong.
>
> [1] https://tools.ietf.org/html/rfc6749#section-5.2
>
>
> Thanks,
> Nila.
>
> --
> Nilasini Thirunavukkarasu
> Software Engineer - WSO2
>
> Email : nilas...@wso2.com
> Mobile : +94775241823 <+94%2077%20524%201823>
> Web : http://wso2.com/
>
>
> 
>



-- 
Maduranga Siriwardena
Senior Software Engineer
WSO2 Inc; http://wso2.com/

Email: madura...@wso2.com
Mobile: +94718990591
Blog: *https://madurangasiriwardena.wordpress.com/
*

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Error code unsupported_client_authentication_method in IS-5.4.1

[Nilasini Thirunavukkarasu]

Hi,

In IS-5.4.1 if there is no client authentication in the token request, we
are giving the error code *unsupported_client_authentication_method*.
According to the spec[1], if there is no client authentication or
unsupported client authentication, it will fall under "invalid_client".

invalid_client
   Client authentication failed (e.g., unknown client, no
   client authentication included, or unsupported
   authentication method).  The authorization server MAY
   return an HTTP 401 (Unauthorized) status code to indicate
   which HTTP authentication schemes are supported.  If the
   client attempted to authenticate via the "Authorization"
   request header field, the authorization server MUST
   respond with an HTTP 401 (Unauthorized) status code and
   include the "WWW-Authenticate" response header field
   matching the authentication scheme used by the client.




According to the spec, there is no standard error code like
*unsupported_client_authentication_method.
*Is there any specific reason to introduce a new error code
*unsupported_client_authentication_method *in IS5.4.1?.

Example:-

request:-
curl -H  -k -d "grant_type=client_credentials" -H
"Content-Type:application/x-www-form-urlencoded"
https://localhost:9443/oauth2/token -k

response:-
{"error_description":"Unsupported Client Authentication
Method!","error":"unsupported_client_authentication_method"}

Please correct me if I'm wrong.

[1] https://tools.ietf.org/html/rfc6749#section-5.2


Thanks,
Nila.

-- 
Nilasini Thirunavukkarasu
Software Engineer - WSO2

Email : nilas...@wso2.com
Mobile : +94775241823
Web : http://wso2.com/



___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Cannot find the Doc Site for siddhi-map-csv

[Sriskandarajah Suhothayan]

Thanks, Mahesika and Kalaiyarasi.

@Kalaiyarasi can you also add a sample to SP using CSV.

Regards
Suho

On Tue, Feb 6, 2018 at 11:00 AM, Kalaiyarasi Ganeshalingam <
kalaiyar...@wso2.com> wrote:

> Thanks Maheshika, Now It's working.
>
> Kalaiyarasi Ganeshalingam
> Associate Software Engineer| WSO2
> WSO2 Inc : http://wso2.org
> 
> Tel:+94 076 6792895 <076%20679%202895>
> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
> Blogs : https://kalaiyarasig.blogspot.com/ 
>
> On Tue, Feb 6, 2018 at 8:44 AM, Maheshika Goonetilleke  > wrote:
>
>> Hi Suho
>>
>> My mistake, I have pointed to /docs. Amended it to point to gh-pages.
>> Please check now.
>>
>> On Tue, Feb 6, 2018 at 12:38 AM, Sriskandarajah Suhothayan > > wrote:
>>
>>> @Maheshika Can you cross check if the siddhi-map-csv[1] is properly
>>> enabled with gh-pages site?
>>>
>>> [1] https://github.com/wso2-extensions/siddhi-map-csv/
>>>
>>> On Sat, Feb 3, 2018 at 8:53 PM, Sriskandarajah Suhothayan >> > wrote:
>>>
 I still don’t see the site being fixed !

 This is sloppy!  Please fix ASAP

 On Tue, Jan 30, 2018 at 5:35 PM Kalaiyarasi Ganeshalingam <
 kalaiyar...@wso2.com> wrote:

> Hi all,
>
> Please find the PR [1][2] for this.
>
> [1] https://github.com/wso2-extensions/siddhi-map-csv/pull/5
> [2] https://github.com/wso2-extensions/siddhi-map-csv/pull/4
>
> Regards,
>
> Kalaiyarasi Ganeshalingam
> Associate Software Engineer| WSO2
> WSO2 Inc : http://wso2.org
> 
> Tel:+94 076 6792895 <076%20679%202895>
> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
> Blogs : https://kalaiyarasig.blogspot.com/
> 
>
> On Mon, Jan 29, 2018 at 11:01 PM, Sriskandarajah Suhothayan <
> s...@wso2.com> wrote:
>
>> Why this does not use Siddhi theme like other extensions?
>>
>> On Thu, Jan 25, 2018 at 11:09 AM Kalaiyarasi Ganeshalingam <
>> kalaiyar...@wso2.com> wrote:
>>
>>>
>>> Thanks Maheshika. I will check.
>>>
>>> Kalaiyarasi Ganeshalingam
>>> Associate Software Engineer| WSO2
>>> WSO2 Inc : http://wso2.org
>>> 
>>> Tel:+94 076 6792895 <+94%2076%20679%202895>
>>> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
>>> Blogs : https://kalaiyarasig.blogspot.com/
>>> 
>>>
>>> On Wed, Jan 24, 2018 at 11:05 PM, Maheshika Goonetilleke <
>>> mahesh...@wso2.com> wrote:
>>>
 Hi Kalaiyarasi

 I add the /docs to gh-pages. Please check.

 On Wed, Jan 24, 2018 at 9:26 PM, Kalaiyarasi Ganeshalingam <
 kalaiyar...@wso2.com> wrote:

> + Maheshika.
>
> Kalaiyarasi Ganeshalingam
> Associate Software Engineer| WSO2
> WSO2 Inc : http://wso2.org
> 
> Tel:+94 076 6792895 <+94%2076%20679%202895>
> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
> Blogs : https://kalaiyarasig.blogspot.com/
> 
>
> On Wed, Jan 24, 2018 at 9:06 PM, Kalaiyarasi Ganeshalingam <
> kalaiyar...@wso2.com> wrote:
>
>> Hi Mahesika,
>>
>> Can you generate the gh-page branch for the repo[1].
>>
>> [1] https://github.com/wso2-extensions/siddhi-map-csv
>>
>> Regards,
>> Kalai
>>
>> Kalaiyarasi Ganeshalingam
>> Associate Software Engineer| WSO2
>> WSO2 Inc : http://wso2.org
>> 
>> Tel:+94 076 6792895 <+94%2076%20679%202895>
>> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
>> Blogs : https://kalaiyarasig.blogspot.com/
>> 
>>
>> On Wed, Jan 24, 2018 at 9:00 PM, Kalaiyarasi Ganeshalingam <
>> kalaiyar...@wso2.com> wrote:
>>
>>> Noted.
>>>
>>> Kalaiyarasi Ganeshalingam
>>> Associate Software Engineer| WSO2
>>> WSO2 Inc : http://wso2.org
>>> 
>>> Tel:+94 076 6792895 <+94%2076%20679%202895>
>>> LinkedIn :www.linkedin.com/in/kalaiyarasiganeshalingam
>>> Blogs : https://kalaiyarasig.blogspot.com/
>>> 
>>>
>>> On Wed, Jan 24, 2018 at 9:27 AM, 

Re: [Dev] Bug # IDENTITY-7317

[Ruwan Abeykoon]

Hi Deepak/Pooja,
Thanks for the detailed report on IDENTITY-7317. We will certainly go
through this and provide you the update ASAP.

Cheers,
Ruwan

On Tue, Feb 6, 2018 at 2:09 PM, Pooja Gupta  wrote:

> + Deepak
>
>
>
> *From:* Pooja Gupta
> *Sent:* 06 February 2018 14:09
> *To:* 'dev@wso2.org' ; 'ruw...@wso2.com' 
> *Subject:* Bug # IDENTITY-7317
>
>
>
> Hello,
>
>
>
> I have raised a defect on WSO2 IDP. IDP not handling redirect logout
> response sent from SP to IDP when SP receives unsolicited logout request
> from IDP.
>
>
>
> Appreciate if you could look into the issue. We can talk more for more
> details.
>
>
>
> https://wso2.org/jira/browse/IDENTITY-7317
>
>
>
> Thanks
>
> Pooja
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Posting a plain text message to queue

[dhanya]

Hi,

I am trying to convert an xml message to plain text and post it into a queue
in activemq. However the xml node gets added to the message. I would like to 
know how i can extract just the text nodes from the xml and post to the
queue.

Sample proxy xml:


http://ws.apache.org/ns/synapse;>


http://services.samples/;>





$1























queue
Consumer.Recieve.VirtualTopic.Publish
3


contentType
text/plain


2000
true
consumer



Sample Response posted to queue:
http://ws.apache.org/ns/synapse;>Sample Response

Expected response:
Sample Response

How do i recieve only the text of the message as indicated above?

Thanks and regards,
Dhanya



--
Sent from: http://wso2-oxygen-tank.10903.n7.nabble.com/WSO2-Development-f3.html
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev