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

[#1]

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.

[#2]

Any ideas or suggestions for this type of use case? If its not possible currently perhaps this can be a suggestion for a future roadmap item. Thanks!

[#3]

I believe there is a teams capability coming soon in Edge. I don't work for Apigee but that's what I have heard.

[mattz]

We are also facing the problem with multiple teams working in the same (Apigee) organization and are looking for a solution.

Has anyone good or bad experience with the pattern described above ("API proxy naming convention whereby RBAC allocates API proxies to teams based on an API proxy naming strategy")?

Are there other/better solutions to this problem?

Can we expect full team support in Edge anytime soon?

[sjm2000]

Does anyone have any updates on this?

[#6]

Yes, there are roles for each proxy in old edge UI. One api will be only visible to the users of the role assigned to that api. This is simple and easy.

In new edge UI, in the role only you can add the specific proxies they can see.

[guycrets]

What do you mean with "new edge UI"? Do you refer to Apigee Hybrid?

Question about multiple teams within single tenant remains very relevant. But challenging without e.g. support for regex/patterns in authorizations/role-definitions.

[#8]

In Apigee roles, you have option to add the proxies. The specific roles can see those APIs only. Other APIs will not be visible to users of that role.

When I said new ege ui, means the newer version of Apigee ui that is available for last couple of Apigee versions.