- Configuring the Primary User Stores: This topic explains how the primary user store is set up and configured for your product.
- Configuring the Authorization Manager : This topic explains how the repository (RDBMS) for storing authorization information (role-based permissions) is configured for your product.
- Changing a Password: This topic explains how you can change the admin password using the management console of the product.
|This is the role that has all administrative privileges of the WSO2 product, so all users having this role are admins of the product. You can provide any meaningful name for this role. This role is created in the internal H2 database when the product starts. This role has permission to carry out any actions related to the Management Console. If the user store is read-only, this role is added to the system as a special internal role where users are from an external user store.|
Configures the default administrator for the WSO2 product. If the user store is read-only, the admin user must exist in the user store or the system will not start. If the external user store is read-only, you must select a user already existing in the external user store and add it as the admin user that is defined in the
|This is the username of the default administrator or super tenant of the user store. If the user store is read-only, the admin user MUST exist in the user store for the process to work.|
Do NOT put the password here but leave the default value. If the user store is read-only, this element and its value are ignored. This password is used only if the user store is read-write and the
|The name of the "everyone" role. All users in the system belong to this role.|