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";>
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' ;
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| WSO
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_cli
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.
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 alrea
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
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
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 b
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...
>
>
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 s
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 enab
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
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 pa
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 co
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
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
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
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,
R
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 ver
20 matches
Mail list logo