Re: [Dev] WSO2 Message Broker 3.2.0 RC2 Released !!

[Manorama Perera]

Hi All,

Tested ESB/MB integration.

-Integration using JMS Endpoints and JMS Proxy Services
-Integration using Message Stores and Processors


No issues found.
[+] Stable - go ahead and release

Thanks,
Manorama

On Fri, Apr 21, 2017 at 5:54 PM, Hasitha Amal De Silva 
wrote:

> Hi all,
>
> Tested 800 durable subscribers failing over across a 3 node cluster.
>
> No Issues found.
> [+1] Stable - go ahead and release.
>
> Thanks
>
> On Fri, Apr 21, 2017 at 4:31 PM, Akalanka Pagoda Arachchi <
> darsha...@wso2.com> wrote:
>
>> Hi All,
>>
>> Tested integration with EI 6.1.0.
>>
>> Tested basic publish, consume and failover with EI 6.1.0.
>>
>> No issues found.
>> [+] Stable - go ahead and release
>>
>> Thanks,
>> Akalanka.
>>
>> On Fri, Apr 21, 2017 at 4:30 PM, Pumudu Ruhunage  wrote:
>>
>>> Hi All,
>>> Tested MQTT standalone/clustered basic test scenarios and execute
>>> eclipse Interop test suite.
>>>
>>> No issues found.
>>> [+] Stable - go ahead and release
>>>
>>> Thanks,
>>>
>>> On Thu, Apr 20, 2017 at 6:47 PM, Pamod Sylvester  wrote:
>>>
 Hi Devs,

 This is the 2nd release candidate of WSO2 Message Broker 3.2.0.

 *This release fixes the following issues:*
 *https://wso2.org/jira/browse/MB-1910?filter=13675
 *

 *Known Issues:*
 *https://wso2.org/jira/browse/MB-1757?filter=13676
 *

 
 Please download MB 3.2.0 RC2 and test the functionality and vote. The
 vote will be open for 72 hours or as needed.

 *Source & binary distribution files:*
 https://github.com/wso2/product-mb/releases/tag/v3.2.0-RC2

 *The tag to be voted upon:*
 https://github.com/wso2/product-mb/tree/v3.2.0-RC2


 [+] Stable - go ahead and release
 [-]  Broken - do not release (explain why)

 Thanks and Regards,

 --
 *Pamod Sylvester *

 *WSO2 Inc.; http://wso2.com *
 cell: +94 77 7779495 <077%20777%209495>

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


>>>
>>>
>>> --
>>> Pumudu Ruhunage
>>> Software Engineer | WSO2 Inc
>>> M: +94 779 664493  | http://wso2.com
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Darshana Akalanka Pagoda Arachchi,*
>> *Senior Software Engineer, WSO2*
>> *+94777118016 <+94%2077%20711%208016>*
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Cheers,
>
> Hasitha Amal De Silva
> Senior Software Engineer
> Mobile : +94772037426 <+94%2077%20203%207426>
> Blog: http://devnutshell.tumblr.com/
> WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Manorama Perera
Software Engineer
WSO2, Inc.;  http://wso2.com/
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MSF4J Websocket security token transmit

[Irunika Weeraratne]

Hi Godwin,
Yes we can do it. Can we have a small dicussion on Monday?

Thanks,
Irunika

On Apr 21, 2017 8:00 PM, "Godwin Shrimal"  wrote:

> @adding Thusitha.
>
> As described above currently there is no way to extract headers from
> Session in MSF4J and no interceptor support yet with websocket. Shall we
> add the capability to extract headers from Session ?
>
>
> Thanks
> Godwin
>
>
> On Fri, Apr 21, 2017 at 5:32 PM, Godwin Shrimal  wrote:
>
>> Hi All,
>>
>> Here we are using websocket sever as MSF4J and client as netty, my
>> problem is currently there is no way to extract headers from Session while
>> handshake.
>>
>> Thanks
>> Godwin
>>
>> On Fri, Apr 21, 2017 at 12:21 PM, Ayyoob Hamza  wrote:
>>
>>> Hi
>>> What would be solution if we are to initiate the connection from the
>>> browser itself, AFAIK websocket library for browsers does not support
>>> adding headers.
>>>
>>> Thanks,
>>>
>>> *Ayyoob Hamza*
>>> *Senior Software Engineer*
>>> WSO2 Inc.; http://wso2.com
>>> email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
>>>
>>> On Fri, Apr 21, 2017 at 11:32 AM, Irunika Weeraratne 
>>> wrote:
>>>
 Hi Godwin,
 IMHO the best way to do it using HTTP header. Are you using netty
 directly? If that so there is a way to add necessary headers for the
 initial handshake and we can check them in the server side.

 Thanks,
 Irunika

 *Irunika Weeraratne*
 *Software Engineer | WSO2, Inc. *
 *Email : irun...@wso2.com *
 *LinkedIn : https://lk.linkedin.com/in/irunika
 *
 *Mobile : +94712403314 <+94%2071%20240%203314>*
 *Lean . Enterprise . Middleware*


 On Fri, Apr 21, 2017 at 11:27 AM, Arshardh Ifthikar 
 wrote:

> You can find it here: https://docs.wso2.com/display/
> AM210/Create+a+WebSocket+API
>
> Thanks
>
> On Fri, Apr 21, 2017 at 11:24 AM, Godwin Shrimal 
> wrote:
>
>> Can you please share the relevant API Manager source ?
>>
>>
>> Thanks
>> Godwin
>>
>> On Fri, Apr 21, 2017 at 11:22 AM, Arshardh Ifthikar <
>> arsha...@wso2.com> wrote:
>>
>>> Hi,
>>>
>>> IMHO the best approach would be to send it via a header in the
>>> initial HTTP request used to establish the connection. This is the 
>>> method
>>> we follow to send the access token for websocket APIs in the API 
>>> Manager.
>>>
>>> Thanks
>>> Arshardh
>>>
>>> On Fri, Apr 21, 2017 at 11:11 AM, Godwin Shrimal 
>>> wrote:
>>>
 Hi All,

 What is the best way to transmit a security token in web socket
 while establishing a connection ? Currently we are passing through path
 parameter such as wss://localhost:8080/server/

 Is it secure to sent it via path parameter ? If not what is the
 correct approach ?


 Thanks
 Godwin

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

 mobile: *+94772264165*
 linkedin: *http://lnkd.in/KUum6D *
 twitter: https://twitter.com/godwinamila
 

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


>>>
>>>
>>> --
>>> *Arshardh Ifthikar*
>>> Trainee Software Engineer
>>> WSO2, Inc.
>>> Mobile: +94719806525 <+94%2071%20980%206525>
>>>
>>
>>
>>
>> --
>> *Godwin Amila Shrimal*
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>
>
>
> --
> *Arshardh Ifthikar*
> Trainee Software Engineer
> WSO2, Inc.
> Mobile: +94719806525 <+94%2071%20980%206525>
>


 ___
 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
>>>
>>>
>>
>>
>> --
>> *Godwin Amila Shrimal*
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>
>
>
> --
> *Godwin Amila Shrimal*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>
_

Re: [Dev] MSF4J Websocket security token transmit

[Godwin Shrimal]

@adding Thusitha.

As described above currently there is no way to extract headers from
Session in MSF4J and no interceptor support yet with websocket. Shall we
add the capability to extract headers from Session ?


Thanks
Godwin


On Fri, Apr 21, 2017 at 5:32 PM, Godwin Shrimal  wrote:

> Hi All,
>
> Here we are using websocket sever as MSF4J and client as netty, my problem
> is currently there is no way to extract headers from Session while
> handshake.
>
> Thanks
> Godwin
>
> On Fri, Apr 21, 2017 at 12:21 PM, Ayyoob Hamza  wrote:
>
>> Hi
>> What would be solution if we are to initiate the connection from the
>> browser itself, AFAIK websocket library for browsers does not support
>> adding headers.
>>
>> Thanks,
>>
>> *Ayyoob Hamza*
>> *Senior Software Engineer*
>> WSO2 Inc.; http://wso2.com
>> email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
>>
>> On Fri, Apr 21, 2017 at 11:32 AM, Irunika Weeraratne 
>> wrote:
>>
>>> Hi Godwin,
>>> IMHO the best way to do it using HTTP header. Are you using netty
>>> directly? If that so there is a way to add necessary headers for the
>>> initial handshake and we can check them in the server side.
>>>
>>> Thanks,
>>> Irunika
>>>
>>> *Irunika Weeraratne*
>>> *Software Engineer | WSO2, Inc. *
>>> *Email : irun...@wso2.com *
>>> *LinkedIn : https://lk.linkedin.com/in/irunika
>>> *
>>> *Mobile : +94712403314 <+94%2071%20240%203314>*
>>> *Lean . Enterprise . Middleware*
>>>
>>>
>>> On Fri, Apr 21, 2017 at 11:27 AM, Arshardh Ifthikar 
>>> wrote:
>>>
 You can find it here: https://docs.wso2.com/display/
 AM210/Create+a+WebSocket+API

 Thanks

 On Fri, Apr 21, 2017 at 11:24 AM, Godwin Shrimal 
 wrote:

> Can you please share the relevant API Manager source ?
>
>
> Thanks
> Godwin
>
> On Fri, Apr 21, 2017 at 11:22 AM, Arshardh Ifthikar  > wrote:
>
>> Hi,
>>
>> IMHO the best approach would be to send it via a header in the
>> initial HTTP request used to establish the connection. This is the method
>> we follow to send the access token for websocket APIs in the API Manager.
>>
>> Thanks
>> Arshardh
>>
>> On Fri, Apr 21, 2017 at 11:11 AM, Godwin Shrimal 
>> wrote:
>>
>>> Hi All,
>>>
>>> What is the best way to transmit a security token in web socket
>>> while establishing a connection ? Currently we are passing through path
>>> parameter such as wss://localhost:8080/server/
>>>
>>> Is it secure to sent it via path parameter ? If not what is the
>>> correct approach ?
>>>
>>>
>>> Thanks
>>> Godwin
>>>
>>> --
>>> *Godwin Amila Shrimal*
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94772264165*
>>> linkedin: *http://lnkd.in/KUum6D *
>>> twitter: https://twitter.com/godwinamila
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Arshardh Ifthikar*
>> Trainee Software Engineer
>> WSO2, Inc.
>> Mobile: +94719806525 <+94%2071%20980%206525>
>>
>
>
>
> --
> *Godwin Amila Shrimal*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>



 --
 *Arshardh Ifthikar*
 Trainee Software Engineer
 WSO2, Inc.
 Mobile: +94719806525 <+94%2071%20980%206525>

>>>
>>>
>>> ___
>>> 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
>>
>>
>
>
> --
> *Godwin Amila Shrimal*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>



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

mobile: *+94772264165*
linkedin: *http://lnkd.in/KUum6D *
twitter: https://twitter.com/godwinamila

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

[Dev] [C5][Secure-Vault] Resolve function gives empty char array for alias

[Lakshman Udayakantha]

Hi JayangaD,

For issue [1], While debugging the code, I found that
JKSBasedCipherProvider.doCipher(Cipher cipher, byte[] original) method is
received the same byte array when I decrypt same encrypted string for
both osgi service and cipher tool command line argument. But this returns
an empty array for osgi service and correct decrypted value for command
line arguments case. So the problem may be with the cipher object used. In
case how I defer cipher object used for both scenarios? Or any idea to
narrow down the issue?

[1] https://github.com/wso2/carbon-secvault/issues/32

Thanks,
Lakshman.
-- 
Lakshman Udayakantha
WSO2 Inc. www.wso2.com
lean.enterprise.middleware
Mobile: *0717429601*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Message Broker 3.2.0 RC2 Released !!

[Hasitha Amal De Silva]

Hi all,

Tested 800 durable subscribers failing over across a 3 node cluster.

No Issues found.
[+1] Stable - go ahead and release.

Thanks

On Fri, Apr 21, 2017 at 4:31 PM, Akalanka Pagoda Arachchi <
darsha...@wso2.com> wrote:

> Hi All,
>
> Tested integration with EI 6.1.0.
>
> Tested basic publish, consume and failover with EI 6.1.0.
>
> No issues found.
> [+] Stable - go ahead and release
>
> Thanks,
> Akalanka.
>
> On Fri, Apr 21, 2017 at 4:30 PM, Pumudu Ruhunage  wrote:
>
>> Hi All,
>> Tested MQTT standalone/clustered basic test scenarios and execute
>> eclipse Interop test suite.
>>
>> No issues found.
>> [+] Stable - go ahead and release
>>
>> Thanks,
>>
>> On Thu, Apr 20, 2017 at 6:47 PM, Pamod Sylvester  wrote:
>>
>>> Hi Devs,
>>>
>>> This is the 2nd release candidate of WSO2 Message Broker 3.2.0.
>>>
>>> *This release fixes the following issues:*
>>> *https://wso2.org/jira/browse/MB-1910?filter=13675
>>> *
>>>
>>> *Known Issues:*
>>> *https://wso2.org/jira/browse/MB-1757?filter=13676
>>> *
>>>
>>> 
>>> Please download MB 3.2.0 RC2 and test the functionality and vote. The
>>> vote will be open for 72 hours or as needed.
>>>
>>> *Source & binary distribution files:*
>>> https://github.com/wso2/product-mb/releases/tag/v3.2.0-RC2
>>>
>>> *The tag to be voted upon:*
>>> https://github.com/wso2/product-mb/tree/v3.2.0-RC2
>>>
>>>
>>> [+] Stable - go ahead and release
>>> [-]  Broken - do not release (explain why)
>>>
>>> Thanks and Regards,
>>>
>>> --
>>> *Pamod Sylvester *
>>>
>>> *WSO2 Inc.; http://wso2.com *
>>> cell: +94 77 7779495 <077%20777%209495>
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> Pumudu Ruhunage
>> Software Engineer | WSO2 Inc
>> M: +94 779 664493  | http://wso2.com
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Darshana Akalanka Pagoda Arachchi,*
> *Senior Software Engineer, WSO2*
> *+94777118016 <+94%2077%20711%208016>*
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Cheers,

Hasitha Amal De Silva
Senior Software Engineer
Mobile : +94772037426
Blog: http://devnutshell.tumblr.com/
WSO2 Inc.: http://wso2.com ( lean.enterprise.middleware. )
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Widget generation for the UUF based dashboard component

[Lasantha Samarakoon]

+1 on the idea.

Basically do not use the ID attributes within Handlebar templates since it
is a template and there can be multiple instances. Simply generate
necessary markup using a template, do the necessary modifications and then
push the modified content into the parent DOM. Then run the script to draw
the chart.

*Lasantha Samarakoon* | Software Engineer
WSO2, Inc.
#20, Palm Grove, Colombo 03, Sri Lanka
Mobile: +94 (71) 214 1576
Email:  lasant...@wso2.com
Web:www.wso2.com

lean . enterprise . middleware

On Wed, Apr 19, 2017 at 8:37 PM, Udara Rathnayake  wrote:

>
> While working on the new dashboard UUF component we noticed, there can be
> ID conflicts due to the lack of widget isolation.
>
> Eg:-
> In a widget hbs we declare a simple div so later we can append/draw the
> widget content(graph etc..)
>
>> 
>
>
> ​Then we provide data and config to the VizGrammar library and then draw
> the content inside above defined div.
>
>
>> var lineChart = new vizg(data, config);
>> lineChart.draw("#bar");​
>
>
> *​Problem​*
>
> ​With this approach one can't have multiple instances(with different
> data-source/configs) of the same bar-chart widget.
>
> ​We evaluated some technologies like web-components, shadow-dom in-order
> to overcome this.
> Shadow-dom is a viable solution but with the current implementation of
> VizGrammar we can't directly go with that[1].
>
>
>
> *Current solution*
> As we identified, most of the time above problem can occur with the
> widgets generated through the widget-gen tool where end-users use the same
> templated widget to create multiple instances. Simplest way to solve this
> is to have a placeholder when we define the div ID and within the script,
> then dynamically replace this placeholders with the widget-id(or some other
> unique value) during widget generation process.
>
> [1] Creating a widget web-component using existing charting libraries
>
> --
> Regards,
> UdaraR
>
> ___
> 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

[Dev] confirm cff6ac397dbcf7286609162867fdc2b19ff92a6b

[Suthagar Kailayapathy]

confirm cff6ac397dbcf7286609162867fdc2b19ff92a6b

-- 
*K*AILAYAPATHY *S*UTHAGAR
Undergraduate,
Department of Computer Science & Engineering, University of Moratuwa, Sri
Lanka.
Address :154/2, Navalar Road, Jaffna
Mobile : 077 9543968  <555-7>

 Email : suthagar...@cse.mrt.ac.lk | suthaga...@gmail.com
LinkedIn : http://www.linkedin.com/in/ksuthagar

Blog : https://medium.com/@suthagar23 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MSF4J Websocket security token transmit

[Godwin Shrimal]

Hi All,

Here we are using websocket sever as MSF4J and client as netty, my problem
is currently there is no way to extract headers from Session while
handshake.

Thanks
Godwin

On Fri, Apr 21, 2017 at 12:21 PM, Ayyoob Hamza  wrote:

> Hi
> What would be solution if we are to initiate the connection from the
> browser itself, AFAIK websocket library for browsers does not support
> adding headers.
>
> Thanks,
>
> *Ayyoob Hamza*
> *Senior Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>
>
> On Fri, Apr 21, 2017 at 11:32 AM, Irunika Weeraratne 
> wrote:
>
>> Hi Godwin,
>> IMHO the best way to do it using HTTP header. Are you using netty
>> directly? If that so there is a way to add necessary headers for the
>> initial handshake and we can check them in the server side.
>>
>> Thanks,
>> Irunika
>>
>> *Irunika Weeraratne*
>> *Software Engineer | WSO2, Inc. *
>> *Email : irun...@wso2.com *
>> *LinkedIn : https://lk.linkedin.com/in/irunika
>> *
>> *Mobile : +94712403314 <+94%2071%20240%203314>*
>> *Lean . Enterprise . Middleware*
>>
>>
>> On Fri, Apr 21, 2017 at 11:27 AM, Arshardh Ifthikar 
>> wrote:
>>
>>> You can find it here: https://docs.wso2.com/display/
>>> AM210/Create+a+WebSocket+API
>>>
>>> Thanks
>>>
>>> On Fri, Apr 21, 2017 at 11:24 AM, Godwin Shrimal 
>>> wrote:
>>>
 Can you please share the relevant API Manager source ?


 Thanks
 Godwin

 On Fri, Apr 21, 2017 at 11:22 AM, Arshardh Ifthikar 
 wrote:

> Hi,
>
> IMHO the best approach would be to send it via a header in the initial
> HTTP request used to establish the connection. This is the method we 
> follow
> to send the access token for websocket APIs in the API Manager.
>
> Thanks
> Arshardh
>
> On Fri, Apr 21, 2017 at 11:11 AM, Godwin Shrimal 
> wrote:
>
>> Hi All,
>>
>> What is the best way to transmit a security token in web socket while
>> establishing a connection ? Currently we are passing through path 
>> parameter
>> such as wss://localhost:8080/server/
>>
>> Is it secure to sent it via path parameter ? If not what is the
>> correct approach ?
>>
>>
>> Thanks
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Arshardh Ifthikar*
> Trainee Software Engineer
> WSO2, Inc.
> Mobile: +94719806525 <+94%2071%20980%206525>
>



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

 mobile: *+94772264165*
 linkedin: *http://lnkd.in/KUum6D *
 twitter: https://twitter.com/godwinamila
 

>>>
>>>
>>>
>>> --
>>> *Arshardh Ifthikar*
>>> Trainee Software Engineer
>>> WSO2, Inc.
>>> Mobile: +94719806525 <+94%2071%20980%206525>
>>>
>>
>>
>> ___
>> 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
>
>


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

mobile: *+94772264165*
linkedin: *http://lnkd.in/KUum6D *
twitter: https://twitter.com/godwinamila

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

Re: [Dev] WSO2 Message Broker 3.2.0 RC2 Released !!

[Akalanka Pagoda Arachchi]

Hi All,

Tested integration with EI 6.1.0.

Tested basic publish, consume and failover with EI 6.1.0.

No issues found.
[+] Stable - go ahead and release

Thanks,
Akalanka.

On Fri, Apr 21, 2017 at 4:30 PM, Pumudu Ruhunage  wrote:

> Hi All,
> Tested MQTT standalone/clustered basic test scenarios and execute eclipse
> Interop test suite.
>
> No issues found.
> [+] Stable - go ahead and release
>
> Thanks,
>
> On Thu, Apr 20, 2017 at 6:47 PM, Pamod Sylvester  wrote:
>
>> Hi Devs,
>>
>> This is the 2nd release candidate of WSO2 Message Broker 3.2.0.
>>
>> *This release fixes the following issues:*
>> *https://wso2.org/jira/browse/MB-1910?filter=13675
>> *
>>
>> *Known Issues:*
>> *https://wso2.org/jira/browse/MB-1757?filter=13676
>> *
>>
>> 
>> Please download MB 3.2.0 RC2 and test the functionality and vote. The
>> vote will be open for 72 hours or as needed.
>>
>> *Source & binary distribution files:*
>> https://github.com/wso2/product-mb/releases/tag/v3.2.0-RC2
>>
>> *The tag to be voted upon:*
>> https://github.com/wso2/product-mb/tree/v3.2.0-RC2
>>
>>
>> [+] Stable - go ahead and release
>> [-]  Broken - do not release (explain why)
>>
>> Thanks and Regards,
>>
>> --
>> *Pamod Sylvester *
>>
>> *WSO2 Inc.; http://wso2.com *
>> cell: +94 77 7779495 <077%20777%209495>
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Pumudu Ruhunage
> Software Engineer | WSO2 Inc
> M: +94 779 664493  | http://wso2.com
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Darshana Akalanka Pagoda Arachchi,*
*Senior Software Engineer, WSO2*
*+94777118016*
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] WSO2 Message Broker 3.2.0 RC2 Released !!

[Pumudu Ruhunage]

Hi All,
Tested MQTT standalone/clustered basic test scenarios and execute eclipse
Interop test suite.

No issues found.
[+] Stable - go ahead and release

Thanks,

On Thu, Apr 20, 2017 at 6:47 PM, Pamod Sylvester  wrote:

> Hi Devs,
>
> This is the 2nd release candidate of WSO2 Message Broker 3.2.0.
>
> *This release fixes the following issues:*
> *https://wso2.org/jira/browse/MB-1910?filter=13675
> *
>
> *Known Issues:*
> *https://wso2.org/jira/browse/MB-1757?filter=13676
> *
>
> 
> Please download MB 3.2.0 RC2 and test the functionality and vote. The
> vote will be open for 72 hours or as needed.
>
> *Source & binary distribution files:*
> https://github.com/wso2/product-mb/releases/tag/v3.2.0-RC2
>
> *The tag to be voted upon:*
> https://github.com/wso2/product-mb/tree/v3.2.0-RC2
>
>
> [+] Stable - go ahead and release
> [-]  Broken - do not release (explain why)
>
> Thanks and Regards,
>
> --
> *Pamod Sylvester *
>
> *WSO2 Inc.; http://wso2.com *
> cell: +94 77 7779495 <077%20777%209495>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Pumudu Ruhunage
Software Engineer | WSO2 Inc
M: +94 779 664493  | http://wso2.com

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

Re: [Dev] MSF4J Websocket security token transmit

[Arshardh Ifthikar]

You can find it here:
https://docs.wso2.com/display/AM210/Create+a+WebSocket+API

Thanks

On Fri, Apr 21, 2017 at 11:24 AM, Godwin Shrimal  wrote:

> Can you please share the relevant API Manager source ?
>
>
> Thanks
> Godwin
>
> On Fri, Apr 21, 2017 at 11:22 AM, Arshardh Ifthikar 
> wrote:
>
>> Hi,
>>
>> IMHO the best approach would be to send it via a header in the initial
>> HTTP request used to establish the connection. This is the method we follow
>> to send the access token for websocket APIs in the API Manager.
>>
>> Thanks
>> Arshardh
>>
>> On Fri, Apr 21, 2017 at 11:11 AM, Godwin Shrimal  wrote:
>>
>>> Hi All,
>>>
>>> What is the best way to transmit a security token in web socket while
>>> establishing a connection ? Currently we are passing through path parameter
>>> such as wss://localhost:8080/server/
>>>
>>> Is it secure to sent it via path parameter ? If not what is the correct
>>> approach ?
>>>
>>>
>>> Thanks
>>> Godwin
>>>
>>> --
>>> *Godwin Amila Shrimal*
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94772264165*
>>> linkedin: *http://lnkd.in/KUum6D *
>>> twitter: https://twitter.com/godwinamila
>>> 
>>>
>>> ___
>>> Dev mailing list
>>> Dev@wso2.org
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Arshardh Ifthikar*
>> Trainee Software Engineer
>> WSO2, Inc.
>> Mobile: +94719806525 <+94%2071%20980%206525>
>>
>
>
>
> --
> *Godwin Amila Shrimal*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>



-- 
*Arshardh Ifthikar*
Trainee Software Engineer
WSO2, Inc.
Mobile: +94719806525
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] jquery version used in swagger console

[Ishara Cooray]

Thanks Thusitha.

That implies the vulnerability in jquery1.8.0 ( jQuery which is inside
swagger) is not a threat for the product.

Thanks & Regards,
Ishara Cooray
Senior Software Engineer
Mobile : +9477 262 9512
WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware

On Fri, Apr 21, 2017 at 2:53 PM, Thusitha Kalugamage 
wrote:

> Hi Ishara,
>
> Although there can be jQuery distributions within third party libraries, I
> think we have to make sure that only one jQuery distribution is used
> throughout a product.
> APIM Manager 2.1.0 uses jquery-1.11.3.min.js AFIK which swagger-ui works
> fine with. Thus, jQuery which is inside swagger or any other third party
> library is not called at all.
>
> Hope this helps.
>
> Regards,
>
> On Fri, Apr 21, 2017 at 1:50 PM, Ishara Cooray  wrote:
>
>> Hi,
>>
>> APIM Manager 2.1.0  uses jquery-1.11.3.min.js where as Swagger console
>> embedded in store app uses jquery-1.8.0.min.js
>>
>> When i check browser console while page with the swagger console is
>> loading, i could observe that there is a GET request made to
>> jquery-1.11.3.min.js
>>
>> Wondering what is the jquery min js version using at runtime for swagger
>> console.
>> is the Swagger jquery lib is getting overridden by the products lib since
>> it is the latest version?
>>
>>
>> Thanks & Regards,
>> Ishara Cooray
>> Senior Software Engineer
>> Mobile : +9477 262 9512 <+94%2077%20262%209512>
>> WSO2, Inc. | http://wso2.com/
>> Lean . Enterprise . Middleware
>>
>
>
>
> --
> Thusitha Kalugamage
> *Software Engineer*
> Mobile : +94 (0) 774 074370
> Tel   : +94 (0) 112 145 345
> thusi...@wso2.com
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MSF4J Websocket security token transmit

[Arshardh Ifthikar]

Hi all,

@Godwin, we can get it from the message object received given by the
channel read method in a ChannelInboundHandler [1] inserted to the
pipeline. As an example [2] is how we have done it for the API Manager.

@Ayyoob, The javascript Websocket library does not support adding external
headers. It is a limitation of using this approach. But certain developers
seems to have found work arounds [3]

Thanks

[1] https://netty.io/4.0/api/io/netty/channel/ChannelInboundHandler.html
[2]
https://github.com/wso2/carbon-apimgt/blob/6.1.x/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/handlers/WebsocketInboundHandler.java#L111
[3]
http://stackoverflow.com/questions/4361173/http-headers-in-websockets-client-api/41521871#41521871

On Fri, Apr 21, 2017 at 12:37 PM, Godwin Shrimal  wrote:

> yes, we are using netty client. can you point me how we are reading HTTP
> headers in websocket handshake ? I cant see any api to read http headers
> from session object.
>
>
> Thanks
> Godwin
>
> On Fri, Apr 21, 2017 at 11:32 AM, Irunika Weeraratne 
> wrote:
>
>> Hi Godwin,
>> IMHO the best way to do it using HTTP header. Are you using netty
>> directly? If that so there is a way to add necessary headers for the
>> initial handshake and we can check them in the server side.
>>
>> Thanks,
>> Irunika
>>
>> *Irunika Weeraratne*
>> *Software Engineer | WSO2, Inc. *
>> *Email : irun...@wso2.com *
>> *LinkedIn : https://lk.linkedin.com/in/irunika
>> *
>> *Mobile : +94712403314 <+94%2071%20240%203314>*
>> *Lean . Enterprise . Middleware*
>>
>>
>> On Fri, Apr 21, 2017 at 11:27 AM, Arshardh Ifthikar 
>> wrote:
>>
>>> You can find it here: https://docs.wso2.com/display/
>>> AM210/Create+a+WebSocket+API
>>>
>>> Thanks
>>>
>>> On Fri, Apr 21, 2017 at 11:24 AM, Godwin Shrimal 
>>> wrote:
>>>
 Can you please share the relevant API Manager source ?


 Thanks
 Godwin

 On Fri, Apr 21, 2017 at 11:22 AM, Arshardh Ifthikar 
 wrote:

> Hi,
>
> IMHO the best approach would be to send it via a header in the initial
> HTTP request used to establish the connection. This is the method we 
> follow
> to send the access token for websocket APIs in the API Manager.
>
> Thanks
> Arshardh
>
> On Fri, Apr 21, 2017 at 11:11 AM, Godwin Shrimal 
> wrote:
>
>> Hi All,
>>
>> What is the best way to transmit a security token in web socket while
>> establishing a connection ? Currently we are passing through path 
>> parameter
>> such as wss://localhost:8080/server/
>>
>> Is it secure to sent it via path parameter ? If not what is the
>> correct approach ?
>>
>>
>> Thanks
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Arshardh Ifthikar*
> Trainee Software Engineer
> WSO2, Inc.
> Mobile: +94719806525 <+94%2071%20980%206525>
>



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

 mobile: *+94772264165*
 linkedin: *http://lnkd.in/KUum6D *
 twitter: https://twitter.com/godwinamila
 

>>>
>>>
>>>
>>> --
>>> *Arshardh Ifthikar*
>>> Trainee Software Engineer
>>> WSO2, Inc.
>>> Mobile: +94719806525 <+94%2071%20980%206525>
>>>
>>
>>
>
>
> --
> *Godwin Amila Shrimal*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>



-- 
*Arshardh Ifthikar*
Trainee Software Engineer
WSO2, Inc.
Mobile: +94719806525
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MSF4J Websocket security token transmit

[Godwin Shrimal]

Can you please share the relevant API Manager source ?


Thanks
Godwin

On Fri, Apr 21, 2017 at 11:22 AM, Arshardh Ifthikar 
wrote:

> Hi,
>
> IMHO the best approach would be to send it via a header in the initial
> HTTP request used to establish the connection. This is the method we follow
> to send the access token for websocket APIs in the API Manager.
>
> Thanks
> Arshardh
>
> On Fri, Apr 21, 2017 at 11:11 AM, Godwin Shrimal  wrote:
>
>> Hi All,
>>
>> What is the best way to transmit a security token in web socket while
>> establishing a connection ? Currently we are passing through path parameter
>> such as wss://localhost:8080/server/
>>
>> Is it secure to sent it via path parameter ? If not what is the correct
>> approach ?
>>
>>
>> Thanks
>> Godwin
>>
>> --
>> *Godwin Amila Shrimal*
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: *+94772264165*
>> linkedin: *http://lnkd.in/KUum6D *
>> twitter: https://twitter.com/godwinamila
>> 
>>
>> ___
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> *Arshardh Ifthikar*
> Trainee Software Engineer
> WSO2, Inc.
> Mobile: +94719806525 <+94%2071%20980%206525>
>



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

mobile: *+94772264165*
linkedin: *http://lnkd.in/KUum6D *
twitter: https://twitter.com/godwinamila

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

Re: [Dev] MSF4J Websocket security token transmit

[Godwin Shrimal]

yes, we are using netty client. can you point me how we are reading HTTP
headers in websocket handshake ? I cant see any api to read http headers
from session object.


Thanks
Godwin

On Fri, Apr 21, 2017 at 11:32 AM, Irunika Weeraratne 
wrote:

> Hi Godwin,
> IMHO the best way to do it using HTTP header. Are you using netty
> directly? If that so there is a way to add necessary headers for the
> initial handshake and we can check them in the server side.
>
> Thanks,
> Irunika
>
> *Irunika Weeraratne*
> *Software Engineer | WSO2, Inc. *
> *Email : irun...@wso2.com *
> *LinkedIn : https://lk.linkedin.com/in/irunika
> *
> *Mobile : +94712403314 <+94%2071%20240%203314>*
> *Lean . Enterprise . Middleware*
>
>
> On Fri, Apr 21, 2017 at 11:27 AM, Arshardh Ifthikar 
> wrote:
>
>> You can find it here: https://docs.wso2.com/display/
>> AM210/Create+a+WebSocket+API
>>
>> Thanks
>>
>> On Fri, Apr 21, 2017 at 11:24 AM, Godwin Shrimal  wrote:
>>
>>> Can you please share the relevant API Manager source ?
>>>
>>>
>>> Thanks
>>> Godwin
>>>
>>> On Fri, Apr 21, 2017 at 11:22 AM, Arshardh Ifthikar 
>>> wrote:
>>>
 Hi,

 IMHO the best approach would be to send it via a header in the initial
 HTTP request used to establish the connection. This is the method we follow
 to send the access token for websocket APIs in the API Manager.

 Thanks
 Arshardh

 On Fri, Apr 21, 2017 at 11:11 AM, Godwin Shrimal 
 wrote:

> Hi All,
>
> What is the best way to transmit a security token in web socket while
> establishing a connection ? Currently we are passing through path 
> parameter
> such as wss://localhost:8080/server/
>
> Is it secure to sent it via path parameter ? If not what is the
> correct approach ?
>
>
> Thanks
> Godwin
>
> --
> *Godwin Amila Shrimal*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Arshardh Ifthikar*
 Trainee Software Engineer
 WSO2, Inc.
 Mobile: +94719806525 <+94%2071%20980%206525>

>>>
>>>
>>>
>>> --
>>> *Godwin Amila Shrimal*
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94772264165*
>>> linkedin: *http://lnkd.in/KUum6D *
>>> twitter: https://twitter.com/godwinamila
>>> 
>>>
>>
>>
>>
>> --
>> *Arshardh Ifthikar*
>> Trainee Software Engineer
>> WSO2, Inc.
>> Mobile: +94719806525 <+94%2071%20980%206525>
>>
>
>


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

mobile: *+94772264165*
linkedin: *http://lnkd.in/KUum6D *
twitter: https://twitter.com/godwinamila

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

Re: [Dev] MSF4J Websocket security token transmit

[Ayyoob Hamza]

Hi
What would be solution if we are to initiate the connection from the
browser itself, AFAIK websocket library for browsers does not support
adding headers.

Thanks,

*Ayyoob Hamza*
*Senior Software Engineer*
WSO2 Inc.; http://wso2.com
email: ayy...@wso2.com cell: +94 77 1681010 <%2B94%2077%207779495>

On Fri, Apr 21, 2017 at 11:32 AM, Irunika Weeraratne 
wrote:

> Hi Godwin,
> IMHO the best way to do it using HTTP header. Are you using netty
> directly? If that so there is a way to add necessary headers for the
> initial handshake and we can check them in the server side.
>
> Thanks,
> Irunika
>
> *Irunika Weeraratne*
> *Software Engineer | WSO2, Inc. *
> *Email : irun...@wso2.com *
> *LinkedIn : https://lk.linkedin.com/in/irunika
> *
> *Mobile : +94712403314 <+94%2071%20240%203314>*
> *Lean . Enterprise . Middleware*
>
>
> On Fri, Apr 21, 2017 at 11:27 AM, Arshardh Ifthikar 
> wrote:
>
>> You can find it here: https://docs.wso2.com/display/
>> AM210/Create+a+WebSocket+API
>>
>> Thanks
>>
>> On Fri, Apr 21, 2017 at 11:24 AM, Godwin Shrimal  wrote:
>>
>>> Can you please share the relevant API Manager source ?
>>>
>>>
>>> Thanks
>>> Godwin
>>>
>>> On Fri, Apr 21, 2017 at 11:22 AM, Arshardh Ifthikar 
>>> wrote:
>>>
 Hi,

 IMHO the best approach would be to send it via a header in the initial
 HTTP request used to establish the connection. This is the method we follow
 to send the access token for websocket APIs in the API Manager.

 Thanks
 Arshardh

 On Fri, Apr 21, 2017 at 11:11 AM, Godwin Shrimal 
 wrote:

> Hi All,
>
> What is the best way to transmit a security token in web socket while
> establishing a connection ? Currently we are passing through path 
> parameter
> such as wss://localhost:8080/server/
>
> Is it secure to sent it via path parameter ? If not what is the
> correct approach ?
>
>
> Thanks
> Godwin
>
> --
> *Godwin Amila Shrimal*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Arshardh Ifthikar*
 Trainee Software Engineer
 WSO2, Inc.
 Mobile: +94719806525 <+94%2071%20980%206525>

>>>
>>>
>>>
>>> --
>>> *Godwin Amila Shrimal*
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94772264165*
>>> linkedin: *http://lnkd.in/KUum6D *
>>> twitter: https://twitter.com/godwinamila
>>> 
>>>
>>
>>
>>
>> --
>> *Arshardh Ifthikar*
>> Trainee Software Engineer
>> WSO2, Inc.
>> Mobile: +94719806525 <+94%2071%20980%206525>
>>
>
>
> ___
> 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

[Dev] [IDENTITY-5131] A solution for the possible deadlock due to session cleanup task

[Dinali Dabarera]

Hi All,

There is a public issue reported in [3],  due to a deadlock happened in the
long-running scenario.

This deadlock occurs due the time taken by "deleteSTOREOperationsTask"
operation which is responsible for cleaning session data which is scheduled
daily.

We have currently come up with two solutions for this deadlock problem,

   1. *We can add a property like " start-time" in the identity.xml
   file, In code level we can start the cleanup task during an off-peak time.*
   2. *We can create two stored procedures to handle session data cleanup
   tasks and run them as scheduled jobs during the off-peak hours.*

Here both 1 and 2 have advantages and disadvantages.

In a cluster scenario, if we implement *1 *one server should
only run this task.. if all of them run at the same time, there is a chance
for deadlock.
 If we implement *2, *the clean-up is handled by the data
source itself, without interrupting any IS operations.

What will be the best solution, out of 1 and 2 for this deadlock scenario?
Please leave your ideas on this.

[3] https://wso2.org/jira/browse/IDENTITY-5131

Thank you.!

Regards.

-- 
*Dinali Rosemin Dabarera*
Software Engineer
WSO2 Lanka (pvt) Ltd.
Web: http://wso2.com/
Email : gdrdabar...@gmail.com
LinkedIn 
Mobile: +94770198933 <+94%2077%20019%208933>





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

Re: [Dev] MSF4J Websocket security token transmit

[Abimaran Kugathasan]

Hi Godwin,

You can find the source code of API Manager websocket Inbound Handler here
[1] which reading and validating Authorization header.

[1] :
https://github.com/wso2/carbon-apimgt/blob/6.1.x/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/handlers/WebsocketInboundHandler.java#L177

On Fri, Apr 21, 2017 at 11:32 AM, Irunika Weeraratne 
wrote:

> Hi Godwin,
> IMHO the best way to do it using HTTP header. Are you using netty
> directly? If that so there is a way to add necessary headers for the
> initial handshake and we can check them in the server side.
>
> Thanks,
> Irunika
>
> *Irunika Weeraratne*
> *Software Engineer | WSO2, Inc. *
> *Email : irun...@wso2.com *
> *LinkedIn : https://lk.linkedin.com/in/irunika
> *
> *Mobile : +94712403314 <+94%2071%20240%203314>*
> *Lean . Enterprise . Middleware*
>
>
> On Fri, Apr 21, 2017 at 11:27 AM, Arshardh Ifthikar 
> wrote:
>
>> You can find it here: https://docs.wso2.com/display/
>> AM210/Create+a+WebSocket+API
>>
>> Thanks
>>
>> On Fri, Apr 21, 2017 at 11:24 AM, Godwin Shrimal  wrote:
>>
>>> Can you please share the relevant API Manager source ?
>>>
>>>
>>> Thanks
>>> Godwin
>>>
>>> On Fri, Apr 21, 2017 at 11:22 AM, Arshardh Ifthikar 
>>> wrote:
>>>
 Hi,

 IMHO the best approach would be to send it via a header in the initial
 HTTP request used to establish the connection. This is the method we follow
 to send the access token for websocket APIs in the API Manager.

 Thanks
 Arshardh

 On Fri, Apr 21, 2017 at 11:11 AM, Godwin Shrimal 
 wrote:

> Hi All,
>
> What is the best way to transmit a security token in web socket while
> establishing a connection ? Currently we are passing through path 
> parameter
> such as wss://localhost:8080/server/
>
> Is it secure to sent it via path parameter ? If not what is the
> correct approach ?
>
>
> Thanks
> Godwin
>
> --
> *Godwin Amila Shrimal*
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: *+94772264165*
> linkedin: *http://lnkd.in/KUum6D *
> twitter: https://twitter.com/godwinamila
> 
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


 --
 *Arshardh Ifthikar*
 Trainee Software Engineer
 WSO2, Inc.
 Mobile: +94719806525 <+94%2071%20980%206525>

>>>
>>>
>>>
>>> --
>>> *Godwin Amila Shrimal*
>>> WSO2 Inc.; http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> mobile: *+94772264165*
>>> linkedin: *http://lnkd.in/KUum6D *
>>> twitter: https://twitter.com/godwinamila
>>> 
>>>
>>
>>
>>
>> --
>> *Arshardh Ifthikar*
>> Trainee Software Engineer
>> WSO2, Inc.
>> Mobile: +94719806525 <+94%2071%20980%206525>
>>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Thanks
Abimaran Kugathasan
Senior Software Engineer - API Technologies

Email : abima...@wso2.com
Mobile : +94 773922820


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

[Dev] [APIM] jquery version used in swagger console

[Ishara Cooray]

Hi,

APIM Manager 2.1.0  uses jquery-1.11.3.min.js where as Swagger console
embedded in store app uses jquery-1.8.0.min.js

When i check browser console while page with the swagger console is
loading, i could observe that there is a GET request made to
jquery-1.11.3.min.js

Wondering what is the jquery min js version using at runtime for swagger
console.
is the Swagger jquery lib is getting overridden by the products lib since
it is the latest version?


Thanks & Regards,
Ishara Cooray
Senior Software Engineer
Mobile : +9477 262 9512
WSO2, Inc. | http://wso2.com/
Lean . Enterprise . Middleware
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] [APIM] jquery version used in swagger console

[Thusitha Kalugamage]

Hi Ishara,

Although there can be jQuery distributions within third party libraries, I
think we have to make sure that only one jQuery distribution is used
throughout a product.
APIM Manager 2.1.0 uses jquery-1.11.3.min.js AFIK which swagger-ui works
fine with. Thus, jQuery which is inside swagger or any other third party
library is not called at all.

Hope this helps.

Regards,

On Fri, Apr 21, 2017 at 1:50 PM, Ishara Cooray  wrote:

> Hi,
>
> APIM Manager 2.1.0  uses jquery-1.11.3.min.js where as Swagger console
> embedded in store app uses jquery-1.8.0.min.js
>
> When i check browser console while page with the swagger console is
> loading, i could observe that there is a GET request made to
> jquery-1.11.3.min.js
>
> Wondering what is the jquery min js version using at runtime for swagger
> console.
> is the Swagger jquery lib is getting overridden by the products lib since
> it is the latest version?
>
>
> Thanks & Regards,
> Ishara Cooray
> Senior Software Engineer
> Mobile : +9477 262 9512 <+94%2077%20262%209512>
> WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
>



-- 
Thusitha Kalugamage
*Software Engineer*
Mobile : +94 (0) 774 074370
Tel   : +94 (0) 112 145 345
thusi...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev