Currently for APIs we have the permissions *creator* and *publish*er. Regarding the permissions for API Products, it makes sense to allow those with API publish permissions to be able to create and publish products, since the API Publisher is the business user usually. But after chatting with NuwanD thought it was better to have a separate permission for the product to give a more fine grained permission model to users.
On 5 October 2016 at 15:15, Uvindra Dias Jayasinha <[email protected]> wrote: > *Brief* > > The API Product feature being developed for API Manager allows AP > Publishers to bundle a set of APIs and expose them as a product which will > have its own set of policies that will apply all APIs that are bundled > within the product. API Consumers will have the option of subscribing to > the exposed product which will mean that they are subscribed to all APIs > within the same product. > > *Rationale* > > This will enable the consideration the API as a technical artifact which > will not specify any usage policies and the API Product as a business > artifact which will define what polices will be applied. This will allowing > for, > > 1. Grouping of related APIs together by API Publishers > 2. Packaging the same set of APIs pared with different policies in > different products > 3. API consumers can easily discover and subscribe to all related APIs > at once > > > *Conditions* > > 1. This feature will be implemented without relying on the Governance > Registry. Alternative means will be found for specific features that the > registry is relied upon > 2. The current way that APIs are created and published will so this > feature will ensure backward compatibility. > > > -- > Regards, > Uvindra > > Mobile: 777733962 > -- Regards, Uvindra Mobile: 777733962
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
