With this functionality there is a key difference that gets introduced.
For API Application level throttling, subscriber can choose the
throttling policy he is going to subscribe into.
But for API resource level throttling, subscriber cannot control the
throttling limits. He has to adhere to
I feel this functionality will be required in many other places. Thus
should be designed in a generalized manner.
The most obvious place I can think of right now is, AppFactory deploying
applications into different environments. Same can be applicable for Carbon
Apps as well.
The generalized
On Wed, Jul 17, 2013 at 5:23 PM, Samisa Abeysinghe sam...@wso2.com wrote:
Throttling based on which parameters?
For now we have only considered Access Token + API sub context + HTTP Verb
How does that get mapped into tier?
@ the point of API being published, a tier will be associated to
On Wed, Jul 17, 2013 at 5:26 PM, Sanjeewa Malalgoda sanje...@wso2.comwrote:
Hi,
On Wed, Jul 17, 2013 at 4:58 PM, Lakmali Baminiwatta lakm...@wso2.comwrote:
Hi all,
Currently in APIM, each subscriber can choose any tier when subscribing
to an API. There is no way to limit avaiable tiers to
Some feedback.
Your using the same tree view being used by Registry Explorer. right? If
not, please use the same. The functionality required is almost the same.
'RenameFolder' is missing a space.
String 'Folder' is redundant. Only action names 'Create', 'Rename',
'Delete' would suffice. Do we
+1 for the functionality. But haven't seen that much of traction over WADL
with most of the customers we have dealt with so far.
Swagger (https://developers.helloreverb.com/swagger/) on the other hand is
much more widely accepted IMO. WSO2 AM 1.4.0 has the initial integration
done with Swagger.
this as of now.
etc. on a time window.
Thanks,
Sanjeewa
On Wed, Jul 17, 2013 at 5:44 PM, Sumedha Rubasinghe sume...@wso2.com
wrote:
On Wed, Jul 17, 2013 at 5:23 PM, Samisa Abeysinghe
sam...@wso2.comwrote:
Throttling based on which parameters?
For now we have only considered
+1. will schedule next week?
On Fri, Jul 26, 2013 at 3:39 PM, Prabath Siriwardena prab...@wso2.comwrote:
Can we please arrange a design review for this. We discussed an
Application concept in IS and we need to see how all these integrate
together..
Thanks regards,
-Prabath
On Fri, Jul
This discussion happened as part of *Enterprise Store* discussion.
Participants: Nuwan, Azeez, Sanjiva, Srinath, NuwanD, Lalaji, Sanjeewa,
Sumedha
*Current Functionality:*
1. At the point of publishing an API, publisher can select the visibility
scope (one of Globally visible, selected tenants,
I think we should wait for Isabelle to provide explanation. I am also not
clear of what is the exact requirement.
Isabelle, This is regarding Feature #72: Extension Point to associate
sequences to inbound/outbound/fault flows . Could you elaborate bit more
please?
On Wed, Jul 31, 2013 at 9:07
*Supported:*
Out of the box support from API Publisher is HTTP Basic Auth (over SSL).
This results following being added to HTTP Header going to backend service.
property name=Authorization expression=fn:concat('Basic ',
base64Encode('user1:password1')) scope=transport/
*TODO:*
In the case of
-richer-oauth-chain-00.txt
The grant type needs to be urn:ietf:params:oauth:grant_type:redelegate
And also - we should not provide a refresh token in the response.
Thanks regards,
-Prabath
On Mon, Sep 9, 2013 at 9:36 PM, Sumedha Rubasinghe sume...@wso2.comwrote:
*Pattern
Prabath,
AM's scope handling is not fully complaint with OAuth spec. The (valid)
scopes that will reach this particular block is either 'PRODUCTION' or
'SANDBOX'.
These two values have a special meaning in determining the endpoint
addresses in API gateway.
We will fix this with proper scope
be simple as changing this in
gateway.
Thanks regards,
-Prabath
On Fri, Oct 4, 2013 at 11:19 AM, Sumedha Rubasinghe sume...@wso2.comwrote:
Prabath,
AM's scope handling is not fully complaint with OAuth spec. The (valid)
scopes that will reach this particular block is either 'PRODUCTION
Senaka,
Search options mentioned by Nuwan were supported in previous API Store
Publisher. We cannot be breaking this feature we used to support. Wasn't
this captured @ product planning?
On Wed, Oct 9, 2013 at 7:37 PM, Nuwan Bandara nu...@wso2.com wrote:
Hi All,
The problem at hand is that
On Mon, Oct 21, 2013 at 12:34 PM, Prabath Siriwardena prab...@wso2.comwrote:
How do we handle SAML2 sessions now..?
I believe we keep it in-memory..
Keep this in-memory won't scale - as these sessions suppose to live long..
and also won't be accessed frequently..
Can we use an LRU cache -
On Mon, Oct 28, 2013 at 7:58 PM, Nuwan Dias nuw...@wso2.com wrote:
+1 for reducing the number of templates and complexities in generating the
synapse configs out of those. Current model does not scale very well.
@Joe, can you share a simple sample of what you are intending to do?
With the
In the API Manager world we have a handler for this. But currently that
gets invoked inside an API element (It also does few more things than
passing bearer token to designated OAuth endpoint).
A simplified version of this can be used for ESB.
But if this is a handler, how do we intend that to
On Wed, Nov 27, 2013 at 12:01 PM, Nuwan Dias nuw...@wso2.com wrote:
On Wed, Nov 27, 2013 at 11:47 AM, Pulasthi Supun pulas...@wso2.comwrote:
Hi,
On Mon, Nov 25, 2013 at 5:53 PM, Nuwan Dias nuw...@wso2.com wrote:
Hi,
We are about to start work on $subject. We have identified 4 locations
On Wed, Dec 11, 2013 at 2:30 PM, Vijayaratha Vijayasingam
rat...@wso2.comwrote:
Hi all;
We try to incorporate Humantasks in our API management process. Currently
, we try to add human interactions for three tasks.
1. Application creation
2. Usersignup process
3. Subscription
Prabath,
Is there any other planned way of supporting self sign up(and associated
role)?
For example is this the same way agreed for social features we are going to
add to UES?
If we move this element from identity.xml into registry as Lalaji
suggested, what will be the migration impliction for
For external users this is part of single story. The fact that these
components are coming from different projects is irrelevant.
So it needs to happen like how you have mentioned.
We can make CloudApp the starting point and execute this logic in there.
On Thu, Jan 23, 2014 at 9:49 AM, Dimuthu
Paul,
Some of these are being considered with in API Management space as well.
Lets me explain existing capabilities future plans.
Although the OAuth2 spec does not mandate sending a new refresh token when
an access token is being
refreshed (http://tools.ietf.org/html/rfc6749#page-10), I feel
I think we should not worry about throttling for anonymous mode @ this
point. Let's assume all applications require authentication and do
throttling based on session ID.
One thing with session ID is the possibility of that being hijacked.
On Tue, Feb 11, 2014 at 12:50 PM, Suresh Attanayaka
We allow defining data sources @ two levels targeting two different
audiences.
Type1:
Data sources defined in master-datasources.xml are used for server's
internal storage requirements. This includes data source definitions like
Registry database, User Store, etc. These data sources are modified
I think we need to consider the real external store effect here. Assumption
on delete possibility is there due to external store being a WSO2 one right
now.
In reality delete will be possible only if external store provides a way
for that.
On Feb 28, 2014 7:33 AM, Lakmali Baminiwatta
Nice !!
Three things:
1. We need to work on graph titles. While going through the graphs I
realized these can be better worded.
2. Let's also try to extend these to drill downs where ever possible.
eg:
Now we show number of API calls/Application (%).
We can extend this such that, when clicked
Dinusha,
Let's schedule a discussion today with Azeez, Shankar Prabath.
On Thu, Apr 10, 2014 at 6:18 AM, Dinusha Senanayaka dinu...@wso2.comwrote:
Hi,
We have identified following ares to be cover with $subject. Additionally
we need to define features that could be useful for users, like
On Thu, Apr 24, 2014 at 8:55 PM, Nuwan Bandara nu...@wso2.com wrote:
Hi Guys,
We discussed to have the Forum inline with the social implementation we
did for ES. We have defined a nice architecture to handle these events,
threaded posts, likes, bubble up functionality etc. Are we deviating
WSO2 API Manager 1.7.0 Released!
WSO2 API Manager team is pleased to announce the release of version 1.7.0
of the Open Source API Manager.
WSO2 API Manager is a platform for creating, managing, consuming and
monitoring APIs. It employs proven SOA best practices to solve a wide range
of API
What is this fix? Is this about checking if g/w cache is enabled?
On Jun 3, 2014 1:45 PM, Gayan Gunawardana ga...@wso2.com wrote:
Hi,
There is an another small issue with org.wso2.carbon.apimgt.core.
APITokenAuthenticator there should be a small logic change. Please verify
it with APIM team
On Thu, Jul 10, 2014 at 2:28 PM, Chan duli...@wso2.com wrote:
Hi guys,
I have been trying to understand how we will proceed with API Everywhere
in a deployment. A typical APIM deployment will have
- Gateway
- Key Manager
- Store and Publisher
How will we deploy API Everywhere?
On a related note, there are generic flow control patterns to deal with
different scenarios. For example there are flow controls to decide what to
happen when in-memory store runs out of memory, or a particular queue runs
out of space or disk runs out of allocated quota.
So it might be a good
+1 for providing the capability.
Are we going to define permissions per environment or are there going to be
static set of environments?
There is a similar mail for Cassandra in [Architecture] Supporting multiple
environments for Cassandra.
IMO permissions you have mentioned are too high level
Rushmin,
Can you also send a mock UI of the resources section that we discussed?
That will make it more clear on how Policy partials URL templates are
mapped.
On Tue, Aug 26, 2014 at 1:48 PM, Rushmin Fernando rush...@wso2.com wrote:
App Manager supports both database driven simple roles based
, Sumedha Rubasinghe sume...@wso2.com
wrote:
Rushmin,
Can you also send a mock UI of the resources section that we discussed?
That will make it more clear on how Policy partials URL templates are
mapped.
On Tue, Aug 26, 2014 at 1:48 PM, Rushmin Fernando rush...@wso2.com
wrote:
App Manager
If you use triggers, you cannot have a database engine independent design.
On Fri, Sep 12, 2014 at 1:21 PM, Asitha Nanayakkara asi...@wso2.com wrote:
According to an offline chat I had with PrabathA SQL triggers should be
avoided since SQL triggers execute outside SQL transactions.
On Thu,
, however we use RDBMS...
Best regards,
Frank
2014-09-12 10:24 GMT+02:00 Sumedha Rubasinghe sume...@wso2.com:
If you use triggers, you cannot have a database engine independent
design.
On Fri, Sep 12, 2014 at 1:21 PM, Asitha Nanayakkara asi...@wso2.com
wrote:
According to an offline chat
Malintha,
Few suggestions:
#1:
I think AuthenticationAdmin Service is special compared to other services.
For example, if I do a call to get all pending human tasks, the call would
first get authenticated then go to relevant service. So I don't think
Authentication Admin Service is a good
Ruchira/Sameera/Manu,
AFAIK we do not have a specific folder to keep JS libraries related to BE
functionality in the current Jaggery App Structure. Only libraries I have
seen (could be wrong) are in themes/{theme name}/lib.
But these libraries are mostly related to UI presentation.
If I am
This came up during the graph review we had on app manager and API manager
yesterday as well.
In order to get this working, we need to have D3 JS library included.
We already have gone through multiple graph libs and have stopped at plot.
So if we need to have this, we need to do a full analysis
Munasinghe, Inosh Perera, Sumedha
Rubasinghe, Srinath Perera, Manoj Gunawardena
1. Develop components in a separate repo, But for the movement it's
develop as a module inside CDM. Later move to a separate repo.
2.Develop common interface in the core, to cater all core
functionalities
Dulitha,
There is existing implementation to support i18n in Jaggery. Why don't you
sync up with Jaggery team and improve/fix what's already there?
On Fri, Dec 19, 2014 at 7:11 AM, Dulitha Wijewantha duli...@wso2.com
wrote:
Hi guys,
I have been thinking about localization for bit and thought
This is already included in AM 1.9.0 plan and already being worked out.
On Fri, Jan 23, 2015 at 9:01 AM, Prabath Abeysekera praba...@wso2.com
wrote:
Hi Everyone,
Just wondering where we are on $subject and if we've got any plans to
support this anytime soon.
I believe, CDM has a definite
Any particular reason for securing product APIs using Basic Auth?
Products like G-Reg, CDM are using OAuth 2.0 tokens for this instead.
On Tue, Jan 27, 2015 at 11:53 AM, Gihan Anuruddha gi...@wso2.com wrote:
Hi All,
We are going to use a set of REST API [1] to communicate with the data
I need to create a UI component using new Jaggery based model.
Where can I find the how to get started?
Dulitha shared me following.
https://docs.google.com/a/wso2.com/document/d/1YF62nd8Ony8P3_c1w6NmLCH8cznv7Ky0cla3BivIEiE/edit
But it only has concepts does not tell me when to do, where to
Why not make this something like,
GET apps/mobile/v1 - gives a list of all apps
GET apps/mobile/v1/query - gives a matching app list
GET apps/mobile/v1/query/limit/no of apps - limits the list of apps
shown
- Its more RESTy.
- will also facilitate other type of app downloads
What is the offset
Apps for download should be protected with same privileges as rights to
install.
How was this done in EMM 1.0.0?
Write a Jaggery module control access to mobile apps folder.
On Fri, Mar 13, 2015 at 11:08 AM, Chathura Dilan chathu...@wso2.com wrote:
Hi Dilshan,
AFAIK devices directly access
Ruwan,
I have create the Redmine ticket (https://redmine.wso2.com/issues/3822) for
internal tracking the public JIRA (https://wso2.org/jira/browse/APPM-643)
as well.
On Mon, Mar 16, 2015 at 1:46 PM, Ruwan Abeykoon ruw...@wso2.com wrote:
Hi All,
It seems that the SVG diagram missing the text.
Ruwan,
As discussed, let's add this capability in an extensible manner. So that we
will not limit application discovery to WSO2's application server.
On Mon, Mar 16, 2015 at 10:38 AM, Ruwan Abeykoon ruw...@wso2.com wrote:
Hi All,
I am in the process of adding a feature to AppManager to
The idea here is to eliminate the manual steps performed in
https://docs.wso2.com/display/AM180/Publishing+API+Runtime+Statistics
We did a review little while ago and it seems there is a similar
functionality available for AS DSS (as mentioned in
Hi Sinthuja,
Any plans to update how these endpoints are secured?
I have a requirement where data needs to be published to BAM/CEP by
randomly provisioned unreliable clients. So using username/password would
not work.
On Thu, Mar 26, 2015 at 1:04 PM, Sinthuja Ragendran sinth...@wso2.com
wrote:
On Mon, May 4, 2015 at 8:30 PM, Dinusha Senanayaka dinu...@wso2.com wrote:
Hi,
We thought of doing some changes to current versioning support in App
Manager. Current model is similar to Create new version functionality in
API Manager. All versions are appeared on store (unless previous
.
-
*Isabelle Mauny*
VP, Product Management - WSO2, Inc. - http://wso2.com/
On Mon, May 4, 2015 at 5:35 PM, Sumedha Rubasinghe sume...@wso2.com
wrote:
On Mon, May 4, 2015 at 8:30 PM, Dinusha Senanayaka dinu...@wso2.com
wrote:
Hi,
We thought of doing some changes to current
Rushmin,
How about implementing a sharing model for XACML scripts (aka policies)?
for example, when we create filters in JIRA, we either keep them to ourself
or decide to share it with a selected group/users. Why not follow the same
model? That feel more natural.
We follow a similar approach for
Pulasthi,
Sorry for the late reply. But check how API Manager and App Manager has
implemented workflow support.
It has been implemented in a generic way that can be used by other products.
API Manager's workflow support was added about 1.5 years ago.
On Sat, Apr 4, 2015 at 5:31 PM, Pulasthi
Sajith,
Can you make this only applicable to selected web apps only?
On Tue, Apr 7, 2015 at 8:41 PM, Sajith Abeywardhana saji...@wso2.com
wrote:
Hi All,
If webpage containing relative path content there is a problem in gateway
side in AppM. Please find the full analysis in dev mailing list -
On Tue, Apr 7, 2015 at 9:35 PM, Sumedha Rubasinghe sume...@wso2.com wrote:
Sajith,
Can you make this only applicable to selected web apps only?
No need of doing this. :)
The handler will be added to main sequence. That is where all unresolved
requests would go.
On Tue, Apr 7, 2015 at 8
.
On Apr 7, 2015 11:42 PM, Manuranga Perera m...@wso2.com wrote:
For apps that support context change via config (eg am store) this feature
have to be disabled, right?
On 7 Apr 2015 23:07, Sumedha Rubasinghe sume...@wso2.com wrote:
On Tue, Apr 7, 2015 at 9:35 PM, Sumedha Rubasinghe sume...@wso2
Prabath,
I think this has some overlaps and improvements compared to what we have
done for API Manager about 2 years ago.
Let's have a discussion on how to bring best of both worlds.
On Wed, Jul 15, 2015 at 12:49 AM, Prabath Siriwardena prab...@wso2.com
wrote:
Hi Isabelle,
As per the offline
Hi,
I tested the latest pack.
I enabled OData on RDBMSSample.
I was able to access following endpoints and get results as expected.
https://localhost:9443/odata/RDBMSSample/default
https://localhost:9443/odata/RDBMSSample/default/CUSTOMERS
But following did not work. May be my filter criteria is
Hi Srinath,
Here is a brief update on ongoing work.
- IoT Server had both batch real time analytics samples done using BAM
CEP.
- EMM release planned on Oct will ship with mobile analytics
- Now we are integrating DAS @ the CDMF level so that all DAS core
functionalities will be available for
*Problem:*
All our products contain samples that work out of the box. Even on EMM,
agents get installed on to commonly available Android/iOS/Windows devices.
But providing this experience in IoT Server is difficult due to needing a
physical device. And even if a user possess a device, chances are
Prabath,
API Manager has the same setup and it uses a Thrift client for the same (in
the place of using a stub for admin service)
Can't we use the same Thrift server/client pattern?We had a similar
situation in BAM data publisher. There also we used Thrift for performance
reasons.
Stubs are known
On Fri, Nov 20, 2015 at 5:20 PM, Isuru Perera wrote:
> As I mentioned, in Tomcat Valve, we get some details from the User-Agent
> header.
>
> See following code from WebAppMonitoringPublisherValve.java
>
Amila,
It does not sound correct for a multi tenant system right?
I think the solution should be making car deployment automatic @ the tenant
creation level.
On Thu, Jun 23, 2016 at 11:52 AM, Amila Maha Arachchi
wrote:
> All,
>
> Recently I learned following in a discussion
On top of this, we can provide 'session activity' to end users. That will
eliminate some of security concerns
On Tue, Feb 2, 2016 at 3:50 PM, Dinusha Senanayaka wrote:
> Hi All,
>
> *How do we handle authenticated user session currently*
>
> We use Hazelcast cache in the
If we introduce a state to user (like what we have done for access tokens)
this problem can be easily solved at the first level.
Then it's just a matter of deciding what to do with removed users and their
data later on as a clean up task by infra.
On Feb 26, 2016 11:30 AM, "Rasika Perera"
Maheshakya,
Can you check the status of cloud status monitor with Cloud team first?
This was originally written for Stratos.
It's doing the same thing (endpoint monitoring)
We had a similar discussion sometime ago and conclusion was we will share
the same functionality. At that time status
Invite NuwanD from API Manager, Johann & PrabathS as well.
On Fri, Jan 22, 2016 at 10:53 AM, Pumudu Ruhunage wrote:
> Hi Ayyoob,
> +1 for the implementation.
> Can you please schedule a code review meeting for this implementation?
> Please invite MB team for the review meeting
Shavantha,
Can you go through the documentation and getting started guide?
https://docs.wso2.com/display/IoTS100/Getting+Started+with+WSO2+IoT+Server
https://docs.wso2.com/display/IoTS100/Quick+Start+Guide
On Mon, Feb 15, 2016 at 5:13 PM, Ruwan Yatawara wrote:
> Sure
My take on this is slightly different.
First @ a conceptual level when we say IoT Server can be extended by a
plugin, we should have a clear definition of that plugin to have X, Y, Z
capabilities. So I feel having analytics @ device type definition level
(conceptually) is not a problem.
Going by
data IoTS captured? ( or is it for future releases?) IMO that will add
> lot of values to the story.
>
> --Srinath
>
> On Tue, May 17, 2016 at 10:59 AM, Sumedha Rubasinghe <sume...@wso2.com>
> wrote:
>
>>
>>
>> On Tue, May 17, 2016 at 10:45 AM, Srinath Per
On Tue, May 17, 2016 at 10:45 AM, Srinath Perera wrote:
>
>1. When you land on the doc, it is not clear where you should go
>
> Planning to fix this Srinath.
>
>1. There is a quick start guide and "Getting started with IoTS" server
>2. in #2 "Start the Virtual
Ruwan,
Some related thoughts..
1. From product (AM in this case) we are calling two systems (for stat
collection and log event collection). So IMO, we should rather be using two
account to do so. I know we are pushing data to DAS in the end. But That is
irrelevant at this level IMO. And using
Geesara,
This is a model that should be coming out of Dashboard perspective.
If we take a look @ basic building blocks of DS, its (similar to what you
have mentioned)
- Gadget
- Dashboard
- Wizards
- Dashboard Admin panel
- etc
Each of these elements should have a permission model associated per
Resending my reply as it got blocked.
On Wed, Sep 7, 2016 at 2:34 AM, Shammi Jayasinghe wrote:
> Hi,
>
> WSO2 always asks to enable sticky sessions in a distributed setup which
> has multiple key manager nodes. According to my understanding, We needs to
> have this since there
On Fri, Sep 9, 2016 at 11:24 AM, Anusha Jayasundara
wrote:
> Hi Geesara,
>
> I used Haar full body cascade and HoG pedestrian detection cascade, In
> Haar full body cascade they have mentioned that, upper body detection,
> lower body detection and full body detection is there
Harsha,
If we take a vanilla API manager distribution and deploy an API there can
we call it an API product?
On Aug 24, 2016 9:27 AM, "Harsha Kumara" wrote:
>
>
> On Tue, Aug 23, 2016 at 3:07 PM, Sanjeewa Malalgoda
> wrote:
>
>> Hi All
>>
>> Intention of
Sanjeewa,
What if we think similar to creating a feature (Carbon) containing
everything need by selected API(s)?
In that approach, steps that need to happen can be summarised into:
1. create a relational mapping of an API(s) and it's associated constructs
(policies, mediation logic, custom
Pretty useful. This also makes the device plugins deployable without
restarting the server.
I believe we can extend the same to write hot deployable device plugins
using Java (no OSGi).
On Tue, Oct 25, 2016 at 9:02 PM, Ayyoob Hamza wrote:
> Hi All,
>
> Current structure for
To elaborate bit more, plugin descriptor would have the operation
definition and mapping to the UI page that should be loaded.
On Thu, Nov 3, 2016 at 1:59 PM, Chathura Dilan wrote:
> Hi All,
>
> As per the offline discussion, We decided to have these UI elements in the
>
Harshan,
The purpose of descriptor was to remove boiler plate code. If there is
anything specific, use the handwritten plugin approach.
If it's not already there, let's make both descriptor and handwritten
plugin to co-exist on a single runtime.
On Thu, Dec 1, 2016 at 1:25 PM, Harshan Liyanage
+1
On Fri, Jan 6, 2017 at 3:23 PM, SajithAR Ariyarathna
wrote:
> Hi All,
>
> We are hoping to do $subject.
>
> *UUF Component:*
>
> Currently a UUF component has two configuration files, 'component.yaml'
> and 'config.yaml'. 'component.yaml' contains APIs entries and bindings
On Thu, Mar 23, 2017 at 8:28 AM, Lakmali Baminiwatta
wrote:
> Hi all,
>
> Prior to C5, we were generating an access token per app created in the
> store using the client_credentials grant type and it was displayed to be
> used as the test tokens. The same was used in the API
Why this has to be special for Android? It's the generic API we provide
from IoT Server. And current API has part of this functionality. Isn't it?
On Thu, Mar 16, 2017 at 8:59 AM, Inosh Perera wrote:
> Hi All,
>
> Based on Charitha's suggestion to have an SDK for developers, I
Hi Ching,
Could you list out the exact set of steps needed to get this to working
please?
On Tue, Mar 7, 2017 at 9:53 AM, Ching Shi wrote:
> Hi all,
>
> OMA Lightweight M2M protocol is from the Open Mobile Alliance for IoT
> device management. This protocol provides,
>
>1.
Hi Wishmitha,
Would leveldb architecture be efficient for a message broker where removing
delivered messages is very frequent?
This requires WSO2 Message Broker to ship leveldb. leveldb (
https://github.com/google/leveldb) has native distributions for platforms.
AFAIC this will take away platform
I tested following:
Virtual firealarm (control operations,analytics - realtime & batch)
Android Device Mgt(enrollment, ring, message)
Device Type creation (HTTP,MQTT)
Device pushing data (via API)
No blockers were found.
[+] Stable - Go ahead and release.
Thanks,
Sumedha
On Mon, Aug 14, 2017
+1 to the idea.
Permission to feature mapping is already happening within JAX-RS
definition. Isn't t?
On Fri, May 5, 2017 at 1:48 AM, Ayyoob Hamza wrote:
> Hi All,
>
> We can share a device group among the users with a specific set of
> permissions(through a Role). However in
There is an OAuth2 token based topic protector done for IoT scenarios.
On Thu, Dec 14, 2017 at 5:25 PM, Kalaiyarasi Ganeshalingam <
kalaiyar...@wso2.com> wrote:
> Hi all,
>
> DAS already has MQTT Receiver but It is not enabled for secure MQTT
> Communication. So, now I am going to work on this
tling, securing, analyzing, logging, etc.).
>
> We're going to be moving the APIGW to Ballerina platform. So you can come
> and help with that work - need to write a small OAuth keyserver in
> Ballerina itself. Should be easy .. are you volunteering?
>
> On Thu, Jan 18, 2018 at 1:48 PM, Su
IoT Server to support APIs,
events and Streams. Right now it is built around C4 based API G/W, hence
supporting HTTP only.
So wondering what is the correct path to take...
---
Sumedha Rubasinghe
Director - IoT Architecture,
WSO2
m: +94 773017743
received this message because you are subscribed to the Google Groups
>> "WSO2 IoT Team Group" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to iot-group+unsubscr...@wso2.com.
>> For more options, visit https://groups.google.com/a/
support powered by Siddhi runtime everything
will fall in to a single picture..
On Thu, Jan 18, 2018 at 1:33 PM, Sanjiva Weerawarana <sanj...@wso2.com>
wrote:
> Um .. Ballerina?
>
> On Thu, Jan 18, 2018 at 1:28 PM, Sumedha Rubasinghe <sume...@wso2.com>
> wrote:
&g
roduct-iots/milestone/19?closed=1
> [12] https://github.com/wso2/product-iots/milestone/20?closed=1
>
> Regards,
> The WSO2 IoT Team.
>
> --
> With Regards,
>
> *Rasika Perera*
> Senior Software Engineer
> LinkedIn: http://lk.linkedin.com/in/rasika90
>
> <
Installed on a remote machine against MySQL 5.5.
Tested
-Device type API
-Message broker functionality
-stream processing
[+] Stable - Go ahead and release
On Mar 2, 2018 3:02 AM, "Rasika Perera" wrote:
Hi Devs,
We are pleased to announce the release candidate of WSO2 IoT
97 matches
Mail list logo