Re: [Architecture] OAuth Life cycle in client side tool of APIM import/export

2016-08-19 Thread Dinusha Senanayaka
On Fri, Aug 19, 2016 at 5:38 PM, Nuwan Dias wrote: > > > On Fri, Aug 19, 2016 at 5:20 PM, Dinusha Senanayaka > wrote: > >> >> >> On Fri, Aug 19, 2016 at 2:35 PM, Nuwan Dias wrote: >> >>> >>> >>> On Fri, Aug 19, 2016 at 1:40 PM, Sanjeewa

Re: [Architecture] OAuth Life cycle in client side tool of APIM import/export

2016-08-19 Thread Nuwan Dias
On Fri, Aug 19, 2016 at 5:20 PM, Dinusha Senanayaka wrote: > > > On Fri, Aug 19, 2016 at 2:35 PM, Nuwan Dias wrote: > >> >> >> On Fri, Aug 19, 2016 at 1:40 PM, Sanjeewa Malalgoda >> wrote: >> >>> The purpose of implementing client tool is

Re: [Architecture] OAuth Life cycle in client side tool of APIM import/export

2016-08-19 Thread Dinusha Senanayaka
On Fri, Aug 19, 2016 at 2:35 PM, Nuwan Dias wrote: > > > On Fri, Aug 19, 2016 at 1:40 PM, Sanjeewa Malalgoda > wrote: > >> The purpose of implementing client tool is to ease admins/devopts task. >> If we think of end user point of view(api creator) client

Re: [Architecture] OAuth Life cycle in client side tool of APIM import/export

2016-08-19 Thread Nuwan Dias
On Fri, Aug 19, 2016 at 3:05 PM, Bhathiya Jayasekara wrote: > Hi Kaveesha/Nuwan, > > On Fri, Aug 19, 2016 at 2:35 PM, Nuwan Dias wrote: > >> >> >> On Fri, Aug 19, 2016 at 1:40 PM, Sanjeewa Malalgoda >> wrote: >> >>> The purpose of

Re: [Architecture] OAuth Life cycle in client side tool of APIM import/export

2016-08-19 Thread Sanjeewa Malalgoda
If we are using existing publisher/store APIs then we cannot do same like you mentioned. But don't we zip separate service side web application for import/export? If so we can apply basic oauth for that while having oauth for store/publisher. On Fri, Aug 19, 2016 at 2:35 PM, Nuwan Dias

Re: [Architecture] OAuth Life cycle in client side tool of APIM import/export

2016-08-19 Thread Bhathiya Jayasekara
Hi Kaveesha/Nuwan, On Fri, Aug 19, 2016 at 2:35 PM, Nuwan Dias wrote: > > > On Fri, Aug 19, 2016 at 1:40 PM, Sanjeewa Malalgoda > wrote: > >> The purpose of implementing client tool is to ease admins/devopts task. >> If we think of end user point of view(api

Re: [Architecture] OAuth Life cycle in client side tool of APIM import/export

2016-08-19 Thread Nuwan Dias
On Fri, Aug 19, 2016 at 1:40 PM, Sanjeewa Malalgoda wrote: > The purpose of implementing client tool is to ease admins/devopts task. If > we think of end user point of view(api creator) client tool do not help > much. > I don't believe usual API creator, publishers will use

Re: [Architecture] OAuth Life cycle in client side tool of APIM import/export

2016-08-19 Thread Sanjeewa Malalgoda
The purpose of implementing client tool is to ease admins/devopts task. If we think of end user point of view(api creator) client tool do not help much. I don't believe usual API creator, publishers will use this client much. If we need to let them to export API then we should give them UI option.

[Architecture] OAuth Life cycle in client side tool of APIM import/export

2016-08-19 Thread Kaveesha Perera
Hi all, Currently I'm working on a client side tool that consumes REST APIs for API import/export feature of APIM (Refer to my previous email labeled [1]). There OAuth life cycle goes as follows. User asked to give a application name on the configuration file.Using that, tool create a client