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

Version 1 Current »

User management capability comes bundled with the WSO2 Carbon platform and facilitates the management and control of user accounts and roles at different levels. Since it is integrated into the core Carbon platform, user management capability is available by default in all WSO2 Carbon-based products.

You can log in to the Management Console of the API Manager as an admin user and create custom roles with different levels of permission. These roles can then be assigned to different users according to your requirement. We have identified three distinct community roles, which are typically used in many organizational situations, when carrying out different operations in the API Publisher and API Store. They are as follows:

  • creator: A creator is typically a person in a technical role who understands the technical aspects of the API (interfaces, documentation, versions, how it is exposed by API gateway) and uses the API Publisher Web application to provision APIs into the API store. The creator uses the API store to consult ratings and feedback provided by API users. Creator can add APIs to the store but cannot manage their life cycles (i.e. make them visible to the outside world).
  • publisher: A publisher typically manages a set of APIs across the enterprise or business unit and controls the API lifecycle and monetization aspects. The publisher also analyzes usage patterns for APIs and has access to all API statistics.
  • consumer : A consumer uses the API store to discover APIs, consult the documentation and forums as well as rate/comment on the API. He/she subscribes to APIs to obtain an API key.

Given above are example roles which we refer to throughout this documentation. For instructions on creating them, refer to section Managing Users and Roles. Using the same instructions, you can also create additional roles according to your requirements.

  • No labels