Re: [Architecture] Securing Stream Processor API through OAuth2

2017-10-30 Thread Mohanadarshan Vivekanandalingam
On Mon, Oct 30, 2017 at 12:50 PM, Damith Wickramasinghe wrote: > Hi Niveathika, > > Are we securing event simulator apis as well ? > We have to secure that as well. IMO, all the core APIs need to be secured. Thanks, Mohan > > Regards, > Damith > > On Mon, Oct 30, 2017 at

Re: [Architecture] Securing Stream Processor API through OAuth2

2017-10-30 Thread Shiro Kulatilake
Hi Nivethika, Instead of only considering OAuth2 should we try to make this configurable ? (if not already so) Clients using the different APIs might have a preferred way of securing APIs in an organization and they would want to use the same to access these APIs also. Thank you, Shiro On Mon,

Re: [Architecture] Securing Stream Processor API through OAuth2

2017-10-30 Thread Niveathika Rajendran
Hi, Are we securing event simulator apis as well ? @Damith, yes all APIs will be secured except the authentication API (login/logout) Instead of only considering OAuth2 should we try to make this configurable ? (if not already so) @Shiro, yes this is configurable, please refer[1] on other modes

Re: [Architecture] Securing Stream Processor API through OAuth2

2017-10-30 Thread Damith Wickramasinghe
Hi Niveathika, Are we securing event simulator apis as well ? Regards, Damith On Mon, Oct 30, 2017 at 12:38 PM, Niveathika Rajendran wrote: > Hi all, > > The use case in accessing Stream Processor API's are as follows, > > 1. Dashboard front end APIs > > These are API's

[Architecture] Securing Stream Processor API through OAuth2

2017-10-30 Thread Niveathika Rajendran
Hi all, The use case in accessing Stream Processor API's are as follows, 1. Dashboard front end APIs These are API's which the user users to access dashboards he/she will create. These will be protected by using an Authentication API through which the access token obtained by the login will be