Hi Prabath
In the context of EMM/IoT product, we already have apis implemented, Now it
is matter of documenting them with swagger. Given the fact that swagger has
provided annotation based documenting strategy for already implemented
apis, we can utilize them within EMM/IoT for documentation.
I a
Well, supporting device identity is indeed something that's there in the
product roadmap. However, that I'm afraid is out of the scope of what's
proposed and intended to be discussed within this particular thread.
That said, if you are willing to contribute to the platform WRT getting
device ident
Sorry about that. I thought this needs to be done after the device identity
thing which we talked about doing with IS roadmap.
Regards,
Dilshan
On 29 April 2016 at 13:53, Prabath Abeysekera wrote:
> Well, supporting device identity is indeed something that's there in the
> product roadmap. How
On Thu, Apr 28, 2016 at 3:16 PM, Dilshan Edirisuriya
wrote:
> Hi Prabath,
>
> Just commenting by looking at the EMM/IOT current state (I do agree that
> there needs to be a proper standard on this). Although contract first
> approach looks far more clean, EMM/IOT already have APIs defined. Hence
Hi All,
With the new throttling implementation we are using CEP as the global
throttling engine.
*Implementation*
When API Request comes to the throttle handler, the relevant data is
publish to the CEP. Since all the events are publish to the super tenant
space, we are decided to add filter for
Hi all,
User core related authentication and authorization operations can be
accessed through RealmService. Bellow diagram explains the brief outlook of
the Realm service and respective stores.
*RealmService*
Realm service is the User Core API which is exposed to external users. Each
store can
>
> This part is already there right? or are we talking about a new
>> implementation?
>
>
> Actually in existing implementation token is generated against cookie. It
> is not actually a bearer token just a session id. To generate bearer token
> we have to use SAML grant type.
Just looked at the
>
> But the problem is that each and every time a developer logs an audit
> log, he has to set contextual information.
No need to set MDC each time. Just like CarbonContext approach we can set
it at login time, can't we?
On Fri, Apr 29, 2016 at 12:27 AM, Sameera Jayasoma wrote:
> Yes. We were
Hi all,
*Introduction*
The purpose of this feature is to provide a framework to generate gadgets
where you can plug datasource providers and chart templates.
For an example, you will be able to plug your RDBMS datasource, rest api ,
csv file , real time datsources etc as pluggable providers.
*F
Please see the comments inline.
On Fri, Apr 29, 2016 at 7:52 PM, Tanya Madurapperuma wrote:
> Hi all,
>
> *Introduction*
>
> The purpose of this feature is to provide a framework to generate gadgets
> where you can plug datasource providers and chart templates.
>
> For an example, you will be ab
Can you send the correct git-hub links to these API's? Provided links are
either wrong or packages/modules have been renamed.
On Fri, Apr 29, 2016 at 6:35 PM, Jayanga Kaushalya
wrote:
> Hi all,
>
> User core related authentication and authorization operations can be
> accessed through RealmServi
11 matches
Mail list logo