This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.
Log in to ask a question

Can multiple teams within a company using Apigee only see their own sets of APIs through RBAC?

Posted on 12-13-2017 05:11 AM
Not applicable
Reply posted on --/--/---- --:-- AM

Hello

We have multiple teams using Apigee Edge. These teams are responsible for their own API proxies and are geographically spread. Ideally, we would like each team to only see API proxies they create in the future to isolate projects and ensure no other team accidentally impacts any other teams API proxies.

We are wondering if RBAC can be used to ensure teams can only see API proxies that they create ?

Any suggestions? Can this be based off an API proxy naming convention whereby RBAC allocates API proxies to teams based on an API proxy naming strategy?

Any ideas welcome. We wouldn't want to associate RBAC always for existing proxies, as it should also cater new future API proxies too.

4 7 659
Topic Labels
7 REPLIES 7
Top Solution Authors
View all