Apigee provides a Company entity and the ability to associate Apps and App Developers to a Company giving API consumers flexibility in managing these entities.
When large organizations consume APIs they often quiz if we allow Developers to be associated with a Company. This is usually discussed in the context of Apigee’s monetization enabled setup, but this capability is also available without monetization feature enabled (licensed).
Apigee App developers are typically individuals consuming an API. The Apps registered by them are tightly associated with the developer registration. When the developer is disabled all the associated apps, keys and tokens become invalid and terminate the access to APIs.
When a partner or vendor organization consumes APIs of an enterprise, individual developer accounts presents a handful of challenges.
Looking at it from the partner organization perspective:
- There is no visibility on the number of accounts in Developer Portal when multiple teams have individual Developer accounts.
- There is no easy way of sharing API key and secret through the Portal itself
- Onboarding and especially offboarding a Developer is not trivial without contacting the Developer Portal admins.
- Ability to keep an App live when a Developer account is disabled or offboarded.
There are complementing challenges at the API exposure side as well.
The Company entity allows Developers to be associated with a Company. Any App can be created as a Company App and not a Developer App. This allows the Apps to live even when a Developer account that created the App is disabled or removed.
All of this capability is available out-of-box with no additional configuration or monetization license.
Since Apps and Developers are managed through the Developer Portal, a corresponding Drupal module is available to enable this capability in Drupal based Developer Portals. Further customization of the Developer Portal may be necessary to provide the right look and feel.
LinkedIn
Twitter