Manage Users and Roles¶ The WSO2 Integrator: MI has limited role support without fine-grained permission tree support as in the Enterprise Integrator. In WSO2 Integrator: MI, we have one admin role and all the other roles from primary and secondary user stores are considered non-admin roles. See the topics given below to understand user management in the WSO2 Integrator: MI. User credentials in the MI¶ WSO2 Integrator: MI requires user credentials for authentication and authorization purposes: Authentication for internal APIs Users accessing the management API and related tools (WSO2 Integrator: MI ICP/WSO2 Integrator: MI CLI) for administration tasks should be authenticated. Authentication for integration use cases Some integration use cases require authentication by dynamic username token and similar WS-Security options. If you already have an external RDBMS or LDAP user store with predefined roles, you can have role-based authentication for your WS-Security user cases. User authentication is also required for securing REST API artifacts. Authorization for internal APIs Certain resources of the management API are protected by authorization. Therefore, users should be granted admin privileges to operate those resources. Admin users¶ WSO2 Integrator: MI users with admin privileges can manage other users in an LDAP or RDBMS user store that is connected to the WSO2 Integrator: MI server. These user management tasks include viewing, adding, and removing users. Tip Admin users can basically access any resource (of the WSO2 Integrator: MI's management API) that has authorization privileges enabled. By default, only the users resource of the management API allows authorization, which allows an admin to perform user management. Read more about authorization in the management API. If a user with admin privileges does not exist in your user store, the admin credentials will be created when you invoke the WSO2 Integrator: MI's management API for the first time. That is, when you log in to the WSO2 Integrator: MI server from the CLI tool/ICP server, or directly invoke the management API, the user credentials you use will get stored in the user store and admin privileges will be assigned. An existing admin user can log in to the WSO2 Integrator: MI server from the CLI tool or the ICP server to add new users with admin privileges. An admin user can only be removed by the creator. Non-admin users¶ Users without admin privileges can access the management API, the CLI, and the ICP server to update deployed artifacts, and to view and monitor integration artifacts and logs. Restrict non-admin users from updating the deployed artifacts¶ To restrict the non-admin users from updating the deployed artifacts through management API and CLI, you can add the following configuration to the <MI_HOME>/conf/deployment.toml file. [user_access] make_non_admin_users_read_only = true To restrict the non-admin users from updating the deployed artifacts with the Integration Control Plane (ICP), you can add the following configuration to the <ICP_HOME>/conf/deployment.toml file. [user_access] make_non_admin_users_read_only = true Manage users and roles from the CLI¶ You can use the WSO2 MI CLI to view details of users, add new users, and remove users from the user store. For more information, see Manage Users and see Manage Roles. Manage users and roles from the Integration Control Plane¶ For instructions on managing users and roles using the ICP, see Monitor MI Artifacts and Logs.