Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

How to Manage API Development Teams With WSO2 API Manager

DZone's Guide to

How to Manage API Development Teams With WSO2 API Manager

In this quick post, we look at how this tool can help API development teams build awesome APIs with greater efficiency. Read on for more!

· Integration Zone ·
Free Resource

The State of API Integration 2018: Get Cloud Elements’ report for the most comprehensive breakdown of the API integration industry’s past, present, and future.

WSO2 API Manager recently added a feature to control the visibility and the management of the API publisher interface which allows multiple teams within the same organization to independently develop their APIs without allowing others to edit or modify APIs. Even though separate teams can achieve the same (or higher) level of isolation through multi-tenancy, it is not a viable option for most user scenarios where they need to expose APIs through the same tenant without dealing with the tenant level complexities.

The basic requirement to achieve team level isolation is to create a role per team with the necessary permissions to create and publish APIs. You can do this by logging into the WSO2 API manager carbon console (https://localhost:9443/carbon) and then creating a role for team1, and \ assigning API creation and publishing permissions.

View user roles created within the API manager

Permission assignment to the role created for team1

Once this role is created, the team members related to team1 can be assigned to this role. Once we do that, APIs created by any of the team members of team1 can select the team1 role as the Access control→Restricted by roles option of the publisher when creating the APIs so that the API can only be visible in the publisher portal to any other team members in the same team only (+admin).

API publisher access control

If the team members in another team (group) create an API, those APIs will not be visible to the members of team1 within the publisher portal (if they follow the same steps mentioned above). This will make the team level isolated during API development time.

Even though these APIs are not visible within the publisher portal, the visibility on the Store portal can be different. When the API is created, the user can select the visibility level at the store. That can be done at:

  • Role-based
  • Tenant domain-based
  • Public

Depending on the selected visibility level of the Store side, other team members might also be able to view the API within the store. But they cannot modify the API since it is not visible on the publisher side.

Using this method, an organization can easily manage their multiple API development teams without interfering with each other. This feature is available with API Manager 2.1.0's latest updates.

Your API is not enough. Learn why (and how) leading SaaS providers are turning their products into platforms with API integration in the ebook, Build Platforms, Not Products from Cloud Elements.

Topics:
integration ,api development ,integration platforms

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}