On Wed, Mar 15, 2017 at 12:48 AM, Uvindra Dias Jayasinha
wrote:
> where a api creator wants to hide/view his apis to other api creators"
we do support this, there is a column in AM_API table AM_API_PERMISSION
with default value 7 which means API creator can view/edit/delete his API.
If he does
On Wed, Mar 15, 2017 at 12:48 AM, Uvindra Dias Jayasinha
wrote:
> How can we support this by only sticking to the new permission model? We
> need to make the API visible in the store side but hide it on the publisher
> side(other publisher users).
As I understood, your requirement is to hide an
Hi,
Based on the recent queries we got, users try to bring the tenancy model
for managing APIs. For an example there can be two developers who create
APIs for two departments such as marketing and enginnering. Basic idea is
that those APIs are only visible for particular group in store which we ca
Hi,
AFAIU we apply permission for API entity. API does not know anything about
publisher and store. The permission model (Role/group based ) should handle
the visibility at the store and publisher. The permission assigned to API
should be generic. There should not be separate permissions for publi
On Wed, Mar 15, 2017 at 10:47 AM, Pubudu Gunatilaka
wrote:
> Hi,
>
> Based on the recent queries we got, users try to bring the tenancy model
> for managing APIs. For an example there can be two developers who create
> APIs for two departments such as marketing and enginnering. Basic idea is
> th
On Wed, Mar 15, 2017 at 11:29 AM, Lakmal Warusawithana
wrote:
>
>
> On Wed, Mar 15, 2017 at 10:47 AM, Pubudu Gunatilaka
> wrote:
>
>> Hi,
>>
>> Based on the recent queries we got, users try to bring the tenancy model
>> for managing APIs. For an example there can be two developers who create
>>
