By default, the APIs published in Choreo are visible to anyone who visits the Choreo Developer Portal. By default, Choreo sets the visibility of the API to Public
. However, developers can control the visibility of their APIs by changing the default option to Private
or Restricted
.
Visibility settings control users from viewing and modifying APIs. API visibility can be one of the following options:
-
Public : The API is visible to all in the developer portal.
-
Private : The API is visible to the users who only sign in to the Developer Portal.
-
Restricted: The API is visible to only the user that has the roles that you specify. This option helps developers to enforce fine-grained access control to the API.
- Sign in to the Choreo Console.
- Open a REST API (Service) you have created.
- In the left navigation, click Manage and then Settings.
- Under the General Settings section, select the API visibility from the list:
Public
,Private
, orRestricted
.- To enable fine-grained role-based access control to the API in the Developer Portal, select
Restricted
from the API visibility list. You will see the available roles in your organization in the Visible Roles list. - Select any combination of roles. Only the users with the given roles can access the APIs through the Dev Portal.
- Alternatively, You can create a new role and assign it to an API by following the steps below:
- Click + Create New Role in the list.
- Add the role name and description.
- Click Next.
- Assign the relevant permissions to the new role.
- Click Create.
- Select the newly created role from the Visible Roles list.
- Click the tick to save.
- To enable fine-grained role-based access control to the API in the Developer Portal, select
- Acknowledge the notification about the visibility change, and proceed to change the visibility.