Reputation: 2148
I am creating a library of APIs (let say API A, B and C), and I want to deploy differently for different customers.
Let's say, the customer 1 is able to browse, subscribe and use A and B, and the customer 2 is able to use B and C. But, the most important, I don't want that customer 1 knows about API C, and also, the customer 2 has to ignore API A.
I'm trying 2 methods:
a) Multitenant configuration: This has several issues (see this question), but, even I'm not able to hide the API C (when the customer/tenant 1 goes to subscribe to main store, it sees all APIs)
b) Roles and Scopes restriction (I'm following this post). This has some advantages (fine grained access per resource/operation), but, again, doesn't hide the APIs in store
Upvotes: 1
Views: 297
Reputation: 12512
To control API permissions in publisher, you can use Access Control Support for API Publisher feature.
To control visibility in store, you can use Store Visibility and Subscription Availability feature.
Upvotes: 1