>>
>> [1] - https://docs.wso2.com/display/IS530/Configuring+Claims+
>> for+a+Service+Provider
>>
>> Regards,
>> Omindu.
>>
>> On Wed, Dec 13, 2017 at 3:57 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>> wrote:
>>
>>> Hi All,
&g
://medium.facilelogin.com/thirty-solution-patterns-with-the-wso2-identity-server-16f9fd0c0389
[2]
https://github.com/facilelogin/aratuwa/tree/master/oauth2.0-apps/org.wso2.carbon.identity.oauth.spa
Thanks.
--
Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware
Mobile
;
> I am not clear what are you referring attaching session in the request
> here?
>
>
> Thanks
> Godwin
>
> On Mon, Nov 13, 2017 at 7:04 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi IS Team,
>>
>> Configured SAML 2 SSO in WSO2 IS 5
otely. Any solution for that?
[1]
https://docs.wso2.com/display/IS530/SAML2+Bearer+Assertion+Profile+for+OAuth+2.0+with+WSO2+Travelocity
Thanks,
Dilshani
--
Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware
Mobile : +94773375185
Blog: dilshani.me
<htt
t;> to enable client_credential? Inst this a security risk? The only thing
>>> he needs to do is getting the Client ID and Client Secret, But in Store UI
>>> it only shows those after click Generate Key button.
>>>
>>>
>>>
>>> Thanks and Best Regards,
>>>
using the Generate Keys button,
> client_credentials grant is used to generate the token. Therefore you have
> to enable client_credentials grant if you are generating keys via UI. I
> think this is what Hrasha meant.
>
> On Thu, Nov 9, 2017 at 12:20 AM, Dilshani Subasinghe <dilsh.
h2+-+SAML+Extension+Grant+Type
>
> On Thu, Nov 9, 2017 at 12:01 AM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi APIM/IS Team,
>>
>> I'm working with IS as Key manager setup. (APIM 2.1.0 and
>> wso2is-km-5.3.0). In APIM, while generating keys for Appli
an
> use SAML2 Bearer Grant, Once after the successful authentication, your
> webapps getting SAML response, You can pass that SAML response and generate
> the access token.
>
> Please let know if you are not clear with this.
>
> Thanks
> Godwin
>
>
> On Tue, No
-server-16f9fd0c0389
[2]
https://docs.wso2.com/display/IS530/SAML2+Bearer+Assertion+Profile+for+OAuth+2.0+with+WSO2+Travelocity
Regards,
Dilshani
--
Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware
Mobile : +94773375185
Blog: dilshani.m
ates(SSLSessi
>> onImpl.java:431)
>> at org.apache.commons.httpclient.protocol.SSLProtocolSocketFact
>> ory.verifyHostName(SSLProtocolSocketFactory.java:259)
>> at org.apache.commons.httpclient.protocol.SSLProtocolSocketFact
>> ory.createSocket(SSLProtocolSocketFactory.j
olution-patterns-with-the-wso2-identity-server-16f9fd0c0389
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware
Mobile : +94773375185 <+94%2077%20337%205185>
Blog: dilshani.me
<https://wso2.com/signature>
___
indujayaweera.com
>>> <http://wso2.com/signature>
>>>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
2077%20116%202518>
>> dili...@wso2.com
>>
>>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Menaka Jayawardena*
> *
t;>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sasikala Kottegoda
>>>>> *Senior Software Engineer*
>>>>> WSO2 Inc., http://wso2.com/
>>>>> lean. enterprise. middleware
>> the+Broker+Profile
>>
>> Thanks,
>> Pamod
>>
>> --
>> *Pamod Sylvester *
>>
>> *WSO2 Inc.; http://wso2.com <http://wso2.com>*
>> cell: +94 77 7779495 <077%20777%209495>
>>
>
>
>
> --
> Nandika Jayawardana
>
>
> On Tue, Mar 28, 2017 at 6:33 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi EI Team,
>>
>> As I am working with JMS 2.0 scenarios with integration server, it was
>> found that we should add javax.jms-api-2.0.1.jar
>> <https://drive.goo
dorsed).
As JMS 2.0 jar working fine with JMS 1.x scenarios, can we bundle the
integration server with only JMS 2.0 jar ? That will be more user friendly
as we support JMS 2.0 as inbuilt features.
Any thoughts ?
Thanks
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lea
ps://localhost:9443/wso2/scim/Groups
>
> but the result is stripped of any kind of permission, is it possible to
> assign them through such calls ?
>
>
> Regards,
> Hanen
>
> _______
> Dev mailing list
> Dev@wso2.org
> ht
;
>
> --
> Heshitha Hettihewa
> *Software Engineer*
> Mobile : +94716866386
> <%2B94%20%280%29%20773%20451194>
> heshit...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/lis
ss the
> exception?
>
> [1] http://bugsbydilshani.blogspot.co.uk/2016/07/wso2esbcluster-task-
> scheduling-error.html
>
> --
> Shazni Nazeer
> Associate Technical Lead | WSO2
>
> Mob : +94 37331
> LinkedIn : http://lk.linkedin.com/in/shazninazeer
>
-
>
> containerPort: 9763
>
> protocol: "TCP"
>
> -
>
> containerPort: 9443
>
> protocol: "TCP"
>
> -
>
> containerPort: 10397
>
> protocol: "TC
26, 2016 at 5:01 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:
> Hi Irham,
>
> Thanks a lot for pointing out the solution. Problem solved.
>
> Regards,
> Dilshani
>
> On Wed, Oct 26, 2016 at 4:01 PM, Irham Iqbal <iq...@wso2.com> wrote:
>
>> Hi D
re your node refer mail[1]. Then you can check the
> image pulling manually(login to that node and docker pull).
>
>
> Thanks,
> Iqbal
>
> [1] WSO2 Private Docker Registry
>
> On Wed, Oct 26, 2016 at 3:43 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>
Error response from daemon: Authentication is required: Get
https://dockerhub.private.wso2.com/v2/wso2am/manifests/1.10.0:
unauthorized: authentication required
Any ideas/ suggestions to solve this error?
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|
cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Malintha Fernando
> Software Engineer
> WSO2 Inc. | http://wso2.com
> Mobile : +94 718874922
> Blog : http://blog.malintha.org
>
> Lean . Enterprise . Middleware
>
>
>
>
>
>
>
> _
> Heshitha Hettihewa
> *Software Engineer*
> Mobile : +94716866386
> <%2B94%20%280%29%20773%20451194>
> heshit...@wso2.com
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware
Mobile : +94773375185
Blog: dilshani.me
<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware
Mob
>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sameera Gunarathne
>>>>> Software Engineer, WSO2 Inc. http://wso2.
_
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA *|* WSO2
lean *|* enterprise *|* middleware
Mobile : +9
; Can we set transport.jms.JMSSpecVersion globally (ie: via axis2.xml)?
>
> --
> With regards,
> *Manu*ranga Perera.
>
> phone : 071 7 70 20 50
> mail : m...@wso2.com
>
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google
Hi Manuranga,
Sure, will do. I also identified similar scenarios while testing JMS
Transport service parameters.
Regards,
Dilshani
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Hi all,
Update: Issue can be reproduce with ActiveMQ Client libraries which are
having versions greater than 5.9.
Regards,
Dilshani
On Fri, May 27, 2016 at 4:26 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:
> Hi Nuwan,
>
> When I am going to test JMS parameters accor
.0.0-BETA.
>
> Thanks,
> Nuwanw
>
> On Thu, May 26, 2016 at 2:50 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Nuwan,
>>
>> Thank you for your response. I tried with both
>>
>>
>> *java.naming.provider.url=failover:tcp://local
nuw...@wso2.com> wrote:
> Hi Dilshani,
>
>
> On Thu, May 26, 2016 at 1:35 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Nuwan,
>>
>> Yes I configured jms url with failover. Actually I used failover syntax
>> as u asked me to change
>&g
p://activemq.apache.org/failover-transport-reference.html
>
> Thanks,
> Nuwanw
>
> On Wed, May 25, 2016 at 11:51 AM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi ESB Team,
>>
>> I am testing JMS parameters and identified scenario of missing me
6-05-19 11:25:35,411] INFO - ServiceTaskManager
> InitialReconnectDuration reached to MaxReconnectDuration.
> [2016-05-19 11:25:35,411] ERROR - ServiceTaskManager Reconnection attempt
> : 4 for service : JmsProxy failed. Next retry in 60 seconds
>
> Thanks,
> Nuwanw
>
>
> On Thu, May 19, 201
Noted and reported a jira [1] to cover up fixing the issue.
[1] https://wso2.org/jira/browse/ESBJAVA-4625
Regards,
Dilshani
On Thu, May 19, 2016 at 10:47 AM, Nuwan Wimalasekara <nuw...@wso2.com>
wrote:
> HI Dilshani,
>
> On Wed, May 18, 2016 at 6:27 PM, Dilshani Subasinghe <
define only transport.jms.InitialReconnectDuration, It will
always be multiplied by the transport.jms.ReconnectProgressFactor until it
reach to transport.jms.MaxReconnectDuration. *
Regards,
Dilshani
On Wed, May 18, 2016 at 6:27 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:
>
ReconnectDuration.
>
> transport.jms.ReconnectProgressFactor is set to 2 by default to
> increasing the reconnect interval exponential until it reach
> to transport.jms.MaxReconnectDuration.
>
>
> On Wed, May 18, 2016 at 1:59 PM, Dilshani Subasinghe <dilsh...@wso2.com>
>
nProgressionFactor = 2.0; // default
to [bounded] exponential*
Any clarification on above factors will be really appreciated.
[1] - https://docs.wso2.com/display/ESB500/JMS+Transport
[2] - https://axis.apache.org/axis2/java/transports/jms.html
Thank you.
--
Best Regards,
Adding Chanaka
On Mon, May 16, 2016 at 8:55 AM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:
> Hi all,
>
> Currently I am testing JMS transport parameters of ESB 5.0.0 alpha pack
> with MB 3.1.0 as the broker. While testing that, identified following
> factors:
>
&g
docs.wso2.com/display/ESB470/Proxy+Services
[4] https://docs.wso2.com/display/ESB500/Configure+with+WSO2+Message+Broker
Thank you.
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJw
*
*Warning coming from ESB console not from MB*
On Thu, May 12, 2016 at 3:04 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:
> Hi Devs,
>
> I am testing JMS transport parameters in ESB and using MB as the broker. I
> am little bit confused a
ollows
(Warning is printing per message):
*WARN - AMQConnectionDelegate_8_0 Loading keystore and truststore from
system properties*
Can someone help to understand this behavior ? Is it correct, not to
identify connection factory type ?
Thank you.
--
Best Regards,
Dilshani Subasinghe
Software Engine
nged, but if
>>> doesn't the developer should be able to start debugging without any extra
>>> effort from the tooling side. So is there any possibility in getting this
>>> fixed with this release rather than marking it as an improvement?
>>>
>>> Thank You
act options as they are
having similar functionalities.
Thank you
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware
Mobile: +9477337
alse :
>>
>> --- executed by thread T1 and the
>> same thread will wait till it get the response.
>>--- response is received and same thread T1 takes care
>> of executing mediators after that.
>> --- executed by T1
>>
>> Hope this helps you to unders
nse.
>
> [1] - https://docs.wso2.com/display/ESB490/Call+Mediator
>
>
> Thanks,
> Kathees
>
> On Fri, Apr 1, 2016 at 11:20 AM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi ESB team,
>>
>> In call mediator, there is a separate option ca
g disabled, it
may not act as send mediator.
Can someone help to figure out this ?
Thank you.
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.mi
Hi all,
Any updates on issue?
Regards,
Dilshani
On Thu, Feb 25, 2016 at 10:31 AM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:
> Hi Ravindra,
>
> Yes I doubled checked libraries and It will work properly when
> "Clustering" mode disabled.
>
> Yes, it
Identified this as invalid use case.
Thread closed.
Regards,
Dilshani
On Wed, Mar 23, 2016 at 6:21 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:
> Hi Malaka,
>
> Thanks for clarification. There was an old test case for $subject and I am
> checking validity of that. When
ESB=testcase=ESB-2254
Thank you and Regards,
Dilshani
On Wed, Mar 23, 2016 at 6:14 PM, Malaka Silva <mal...@wso2.com> wrote:
> Hi Dilshani,
>
> Yes we can. But this does not make sense. What is the use case you are
> trying to implement?
>
> On Wed, Mar 23, 2016 at 5
Hi all,
Any ideas or comments on $subject?
Regards,
Dilshani
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F=D=1=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ>
lean.enterprise.middleware
Mobile: +94773
Hi Ravindi,
When testing same configs with ESB 5.0.0 m2 pack [1], it doesn't give exact
error. You can try out. It may be fixed the issue through new pack.
[1] -
https://svn.wso2.org/repos/wso2/scratch/ESB/packs/5.0.0-Releases/5.0.0-M2/wso2esb-5.0.0-M2.zip
Regards,
Dilshani
Hi all,
Any updates on issue?
Regards,
Dilshani
On Wed, Mar 2, 2016 at 3:18 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:
> Hi Malaka,
>
> Thank you and will try to proceed with that in mind. Still ESB having
> different behavior rather than normal JMS Client (Even
On Thu, Mar 10, 2016 at 8:14 AM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:
> Hi ESB Team,
>
> When I am configuring Store mediator, I created an On Store Sequence.
>
>
>
> *http://ws.apache.org/ns/synapse
> <http://ws.apache.org/ns/synapse>">
Hi all,
Added a jira issue[1] for particular error.
[1] - https://wso2.org/jira/browse/ESBJAVA-4474
Regards,
Dilshani
On Mon, Mar 7, 2016 at 2:06 PM, Dilshani Subasinghe <dilsh...@wso2.com>
wrote:
> Hi all,
>
> When testing the feature "JMS 2.0:Delivery Delay&quo
ing in synapse ? Why message processor do
not identify On Store Sequence?
Any clarification on this ? Any help will be highly appreciated.
PS: Attached Synapse Configuration XML.
Thank you.
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.goo
r.java:617)
at java.lang.Thread.run(Thread.java:745)
[1] -
https://docs.google.com/document/d/19vEMJEYBo_iSgo3GoRJ5s4cNtcHvLJmd3G6QnldiGrs/edit
Thank you,
--
Best Regards,
Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/
<http://www.google.com/url?q=http%3A%2F%2Fws
gt;
> On Wed, Mar 2, 2016 at 2:55 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Malaka,
>>
>> Thank you for explanations. I checked configurations and updated
>> accordingly. And also there is a small point to clarify.
>>
>> When
gt; Also in mediation flow non-blocking mediator should be used. eg:- callout
> mediator not send mediator.
>
> On Tue, Mar 1, 2016 at 3:34 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi Malaka,
>>
>> In ESB, JMS Inbound endpoint can configure Ac
uot; ?
I'm using separate JMS Client with "Client_Acknowledge" mode and using it
to test JMSX Delivery Count. But ESB Inbound endpoint doesn't behave like
particular JMS Client (With "Client_Acknowledge" mode).
Can you explain ESB behavior within the particular scenario ?
>
wrote:
> Hi Dilshani,
>
> AFAIK there's no special configuration for this in ESB side. Have you
> copied all the libraries to the workers properly? If so we have to debug
> and see the root cause of the issue.
>
>
> Thanks & Regards,
>
> On Thu, Feb 25, 2016
r issue persist when
> there are multiple subscribers?
>
> Also you must be using esb 5 milestone pack?
>
> On Wed, Feb 24, 2016 at 7:09 PM, Dilshani Subasinghe <dilsh...@wso2.com>
> wrote:
>
>> Hi ESB Team,
>>
>> I am testing new fearure cal
Hi ESB Team,
I am testing new fearure called "JMS 2.0.0 Support"[1] and found an error
in "JMS 2.0 Feature:Shared Topic Subscription". Feature will successfully
functioning in Standalone mode. But it clustering mode, it will provide an
error as follows;
TID: [-1234] [] [2016-02-24 15:30:13,451]
ls needs to be implemented.
>> AFAIK MSMP does not support transactions.
>>
>> [1] https://docs.wso2.com/display/ESB490/JMS+Inbound+Protocol
>> [2] https://docs.wso2.com/display/ESB490/JMS+FAQ
>>
>> On Wed, Feb 17, 2016 at 12:00 PM, Dilshani Subasinghe <dilsh
Hi,
I am working with $subject[1] in QA perspectives and identified relevant
scenarios through given documentations. But that feature titled as " JMS
Transaction support for Store Mediator" and Feature will introduce
"Scheduled Failover Message Forwarding Processor".
Little bit confused with the
67 matches
Mail list logo
