This documentation is for WSO2 Open Banking version 1.3.0. View documentation for the latest release.

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Approach 01: 
    • Create a user.
    • Create a user role and assign it to users. 
  • Approach 02:
    • Create a user role.
    • Create a user and assign one or multiple user roles to the user. 

In this tutorial, we will take the first approach.  

...

titleBefore you begin

...

Let's get started!

Step 01: Create a User Role

Follow the steps below to create a user role:

  1. Click Main > Identity > Users and Roles > Add on the Management Console home screen.
    Image Removed
  2. Click Add New Role
    Image Removed
  3. Enter a role name, e.g, APIConsumer and click Next
    Image Removed
  4. Select the necessary permissions, e.g., Admin Permissions > Manage > Subscribe and click Finish.
    Image Removed
    A success message is displayed.  

Step 02: Create a User

Follow the steps below to create a user:

  1. Click Main > Identity > Users and Roles > Add on the Management Console home screen. 
    Image Removed
  2. Click Add New User.
    Image Removed
  3. Enter the username andthe password that can be used by the user to sign in to WSO2 Open Banking solution.
    Image Removed
  4. Click Next.
  5. Select the user role applicable for the created user, e.g., APIConsumer.
    Image Removed
  6. Click Finish.
    A success message is displayed.

...

The user management feature allows you to create new users and define the permissions granted to each user. You can also configure the user stores that are used for storing data related to user management.

For detailed information on working with user management, see the following sections in the WSO2 Administration Guide:

SectionDescription
Configuring the System AdministratorThe admin user is the super tenant who is able to manage all other users, roles, and permissions in the system by using the management console of the product. Therefore, the user that has admin permissions has to be stored in the primary user store when you start the system for the first time. The documentation on setting up primary user stores explains how to configure the administrator while configuring the user store. The information under this topic explains the main configurations that are relevant to setting up the system administrator.
Configuring the Authorization ManagerAccording to the default configuration in WSO2 products, the users, roles and permissions are stored in the same repository (i.e., the default, embedded H2 database). However, you can change this configuration in such a way that the users and roles are stored in one repository (user store) and the permissions are stored in a separate repository. A user store can be a typical RDBMS, a LDAP, or an external Active Directory. 

The repository that stores permissions should always be a RDBMS. The Authorization Manager configuration in the user-mgt.xml file connects the system to this RDBMS. The information under this topic instructs you through setting up and configuring the Authorization Manager.  

Configuring User Stores

The user management feature allows you to maintain multiple user stores for storing users and their roles. See the following topics for instructions:

Managing Users, Roles and Permissions

The user management functionality is provided by default, and it supports the role-based authentication model where privileges of a user are based on the role attached. For more information on managing users, roles, and permissions see the following sections in the WSO2 Administration Guide.