Unknown macro: {next_previous_links}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

When a particular user creates an API in the API Publisher, s/he can set its visibility to either Public or Restricted by Roles in the Add New API page of the API Publisher Web interface as follows:

This allows you to prevent certain user roles from viewing and modifying APIs created by another user role. The two visibility values mean the following:

  • Public : When the API creator publishes this API to the API Store, it will be visible to all subscribers as well as anonymous users of the API Store.
  • Restricted by Roles : When the API creator publishes this API to the API Store, it will be visible only to specified user roles in the API Store. When Restricted by Roles is selected, a new field called Visible to Roles appears where you can specify the user roles that have access to the API in a comma-separated list (no spaces).

    If you specify the default subscriber role in the Visible to Roles field. Any user who self-subscribes to the API Store will be able to access the API. That is because the API Manager assigns the subscriber role to all users who sign up to the API Store. 

Given below is how visibility levels work for users in different tenant modes:

Visibility in super tenant mode

Subscribers in super tenant mode can see an API depending on its visibility level as follows:

  • Anonymous users : can see APIs with Public visibility
  • Signed-up users : can see all APIs with Public visibility as well as APIs that are Restricted by Roles, give that the user is assigned to the role the API is restricted by.

Visibility in multi-tenant mode

In multi tenant environment, a subscriber can see API Store URLs of existing tenants. Click a URL to browse the tenant's API Store.

A tenant's API Store is the API Store specific to the tenant domain the user belongs to. You can also access it with the URL http://<hostname>/Store?tenant=<tenantdomain.com>. Therefore, the APIs a subscriber sees in multi tenant mode depend on their visibility levels as well as which API Store s/he is looking at. Any subscriber viewing his/her tenant's API Store can see an API depending on its visibility level as follows:

  • Anonymous users: can see APIs that have Public visibility and created within the current user's tenant domain
       
  • Logged in users: can see,  
    • APIs that have Public visibility and created within the current users tenant domain
    • Restricted by Roles APIs created within the current user's tenant domain and are allowed to be accessed by the role of the current user

Go back to Creating an API page .

  • No labels