Page Comparison

For detailed information on configuring users, roles, and permissions, see the following topics.

The following items are things to note before you begin.

• By default, Identity Server comes with the following roles:

  • Admin - Provides full access to all features and controls. By default, the user "Admin" is assigned to both the "Admin" and the "Everyone" roles. The Identity Server does not allow you to configure permissions assigned to the "Admin" role.

  • Everyone - Every new user is assigned to this role by default. It does not include any permissions.
  • System - This role is not visible in the Management Console.
• Only system administrators can add, modify and remove users and roles. To set up administrators, see Configuring the RealmSystem Administrator. 

• Your product has a primary user store where the users/roles that you create using the management console are stored by default. It's default RegEx configurations are as follows. RegEx configurations ensure that parameters like the length of a user name/password meet the requirements of the user store.

  Code Block
  PasswordJavaRegEx-------- ^[\S]{5,30}$ PasswordJavaScriptRegEx-- ^[\S]{5,30}$ UsernameJavaRegEx-------- ^~!#$;%*+={}\\{3,30}$ UsernameJavaScriptRegEx-- ^[\S]{3,30}$ RolenameJavaRegEx-------- ^~!#$;%*+={}\\{3,30}$ RolenameJavaScriptRegEx-- ^[\S]{3,30}$

  When creating users/roles, if you enter a username, password etc. that does not conform to the RegEx configurations, the system throws an exception. You can either change the RegEx configuration or enter values that conform to the RegEx. If you change the default user store or set up a secondary user store, configure the RegEx accordingly under the user store manager configurations in <IS_HOME>/repository/conf/user-mgt.xml file.

• The permission model of WSO2 Identity Server is hierarchical. Permissions can be assigned to a role in a fine-grained or a coarse-grained manner.

  Info
  WSO2 Carbon maintains roles and permissions in the Carbon database, but it can also read users/roles from the configured User Store.