Chapter 20. Security management
Chapter 20. Security management Security management is the process of managing users, groups, and permissions. You can control access to Business Central resources and features from the Business Central Security management page. Business Central defines three types of entities for security management: users, groups, and roles. You can assign permissions to both roles and groups. A user inherits permissions from the groups and roles that the user is a member of. 20.1. Security management providers In the context of security management, a realm restricts access to different application resources. Realms contain information about users, groups, roles, and permissions. A concrete user and group management service implementation for a specific realm is called a security management provider. If the built-in security management providers do not meet the requirements of your application security realm, then you can build and register your own security management provider. Note If the security management provider is not installed, the user interface for managing the security realm is not available. After you install and configure a security management provider, the user and group management features are automatically enabled in the security management user interface. Business Central includes the Red Hat JBoss EAP security management provider which supports realm types based on the contents of the application-users.properties or application-roles.properties property file. 20.1.1. Configuring the Red Hat JBoss EAP security management provider based on property files You can build and register your own Red Hat JBoss EAP security management provider. To use the Red Hat JBoss EAP security management provider based on property files, complete the steps in this procedure. Prerequisites Red Hat JBoss EAP is installed. Procedure To use an existing users or roles property file from the Red Hat JBoss EAP instance, include the following system properties in the EAP_HOME/standalone/configuration/application-users.properties and EAP_HOME/standalone/configuration/application-roles.properties files, as shown in the following example: <property name="org.uberfire.ext.security.management.wildfly.properties.realm" value="ApplicationRealm"/> <property name="org.uberfire.ext.security.management.wildfly.properties.users-file-path" value="/standalone/configuration/application-users.properties"/> <property name="org.uberfire.ext.security.management.wildfly.properties.groups-file-path" value="/standalone/configuration/application-roles.properties"/> The following table provides a description and default value for these properties: Table 20.1. Red Hat JBoss EAP security management provider based on property files Property Description Default value org.uberfire.ext.security.management.wildfly.properties.realm The name of the realm. This property is not mandatory. ApplicationRealm org.uberfire.ext.security.management.wildfly.properties.users-file-path The absolute file path for the users property file. This property is mandatory. ./standalone/configuration/application-users.properties org.uberfire.ext.security.management.wildfly.properties.groups-file-path The absolute file path for the groups property file. This property is mandatory. ./standalone/configuration/application-roles.properties Create the security-management.properties file in the root directory of your application. For example, create the following file: Enter the following system property and security provider name as a value in the security-management.properties file: <property name="org.uberfire.ext.security.management.api.userManagementServices" value="WildflyUserManagementService"/> 20.1.2. Configuring the Red Hat JBoss EAP security management provider based on property files and CLI mode To use the Red Hat JBoss EAP security management provider based on property files and CLI mode, complete the steps in this procedure. Prerequisites Red Hat JBoss EAP is installed. Procedure To use an existing users or roles property file from the Red Hat JBoss EAP instance, include the following system properties in the EAP_HOME/standalone/configuration/application-users.properties and EAP_HOME/standalone/configuration/application-roles.properties files, as shown in the following example: <property name="org.uberfire.ext.security.management.wildfly.cli.host" value="localhost"/> <property name="org.uberfire.ext.security.management.wildfly.cli.port" value="9990"/> <property name="org.uberfire.ext.security.management.wildfly.cli.user" value="<USERNAME>"/> <property name="org.uberfire.ext.security.management.wildfly.cli.password" value="<USER_PWD>"/> <property name="org.uberfire.ext.security.management.wildfly.cli.realm" value="ApplicationRealm"/> The following table provides a description and default value for these properties: Table 20.2. Red Hat JBoss EAP security management provider based on property files and CLI mode Property Description Default value org.uberfire.ext.security.management.wildfly.cli.host The native administration interface host. localhost org.uberfire.ext.security.management.wildfly.cli.port The native administration interface port. 9990 org.uberfire.ext.security.management.wildfly.cli.user The native administration interface username. NA org.uberfire.ext.security.management.wildfly.cli.password The native administration interface user's password. NA org.uberfire.ext.security.management.wildfly.cli.realm The realm used by the application's security context. ApplicationRealm Create the security-management.properties file in the root directory of your application. For example, create the following file: Enter the following system property and security provider name as a value in the security-management.properties file: <property name="org.uberfire.ext.security.management.api.userManagementServices" value="WildflyCLIUserManagementService"/> 20.2. Permissions and settings A permission is an authorization granted to a user to perform actions related to a specific resource within the application. For example, a user can have following permissions: View a page. Save the project. View a repository. Delete a dashboard. You can grant or deny a permission and a permission can be global or resource specific. You can use permissions to protect access to resources and customize features within the application. 20.2.1. Changing permissions for groups and roles in Business Central In Business Central, you cannot change permissions for an individual user. However, you can change permissions for groups and roles. The changed permissions apply to users with the role or that belong to a group that you changed. Note Any changes that you make to roles or groups affect all of the users associated with that role or group. Prerequisites You are logged in to Business Central with the admin user role. Procedure To access the Security management page in Business Central, select the Admin icon in the top-right corner of the screen. Click Roles , Groups , or Users on the Business Central Settings page. The Security management page opens on the tab for the icon that you clicked. From the list, click the role or group you want to edit. All details are displayed in the right panel. Set the Home Page or Priority under the Settings section. Set the Business Central, page, editor, space, and project permissions under the Permissions section. Figure 20.1. Setting the permissions Click the arrow to a resource type to expand the resource type whose permissions you want to change. Optional: To add an exception for a resource type, click Add Exception and then set the permissions as required. Note You cannot add an exception to the Business Central resource type. Click Save . 20.2.2. Changing the Business Central home page The home page is the page that appears after you log in to Business Central. By default, the home page is set to Home . You can specify a different home page for each role and group. Procedure In Business Central, select the Admin icon in the top-right corner of the screen and select Roles or Groups . Select a role or group. Select a page from the Home Page list. Click Save . Note The role or group must have read access to a page before you can make it the home page. 20.2.3. Setting priorities A user can have multiple roles and belong to multiple groups. The Priority setting determines the order of precedence of a role or group. Prerequisites You are logged in to Business Central with the admin user role. Procedure In Business Central, select the Admin icon in the top-right corner of the screen and select Roles or Groups . Select a role or group. Select a priority from the Priority menu, and then click Save . Note If a user has a role or belongs to a group that has conflicting settings, the settings of the role or group with the highest priority applies.
<property name="org.uberfire.ext.security.management.wildfly.properties.realm" value="ApplicationRealm"/> <property name="org.uberfire.ext.security.management.wildfly.properties.users-file-path" value="/standalone/configuration/application-users.properties"/> <property name="org.uberfire.ext.security.management.wildfly.properties.groups-file-path" value="/standalone/configuration/application-roles.properties"/> src/main/resources/security-management.properties <property name="org.uberfire.ext.security.management.api.userManagementServices" value="WildflyUserManagementService"/> <property name="org.uberfire.ext.security.management.wildfly.cli.host" value="localhost"/> <property name="org.uberfire.ext.security.management.wildfly.cli.port" value="9990"/> <property name="org.uberfire.ext.security.management.wildfly.cli.user" value="<USERNAME>"/> <property name="org.uberfire.ext.security.management.wildfly.cli.password" value="<USER_PWD>"/> <property name="org.uberfire.ext.security.management.wildfly.cli.realm" value="ApplicationRealm"/> src/main/resources/security-management.properties <property name="org.uberfire.ext.security.management.api.userManagementServices" value="WildflyCLIUserManagementService"/>