Security app
The Security app is where you manage access in the system by administering users, groups, and roles. Magnolia’s built-in access management system authenticates users to determine who is using the system and provides them with the means to sign into applications. It also authorizes users, ensuring that they have the required permissions for actions such as editing pages. You can use the app for permission reporting, auditing, and troubleshooting why users can’t access the resources they should be able to.
Access the Security app from the App Launcher: Admin > Security.
Subapps
Users
Use the Users subapp to manage the different types of user:
-
Create users.
-
Edit user information such as user name, password, details, e-mail, and language.
-
Assign groups to the user.
-
Assign roles to the user.
-
View the groups and roles assigned to a given user.
The user configuration data is stored in the users workspace below these paths:
System users |
|
Users |
|
Public users |
|
For more information, see Editing user permissions.
Groups
Users sharing similar privileges are organized into groups. The purpose of a group is to define the settings for the group as whole rather than for each individual user. Permissions defined at a group level automatically extend to all its members.
When a role is assigned to a group, all users within that group inherit the permissions associated with the role. This eliminates the need to assign individual roles to each user.
Moreover, by assigning additional groups to the current group, users within the current group inherit both the roles and permissions granted to the groups being added.
See Groups for further information.
Roles
A role is a function a user performs either in the management of Magnolia or as a visitor of a Magnolia website. It reflects the actions and activities assigned to, required, or expected of a user. Specific permissions are granted to enable the functions of a role.
For example, the editor role is responsible for editing content displayed on the site. Permissions granted to this role allow the user to edit the content and submit it for review. The publisher role, on the other hand, is tasked with reviewing the content and publishing it from the author instance to the public instance(s).
Roles have JCR Access Control Lists (ACLs) and Web access permissions. For both the JCR content and Web access, you can define multiple ACLs per role.
To understand how to configure ACLs per role, see Roles and access control lists
Configuration
The Security app is installed by the Security app module.
You can configure the app in /security-app/apps/security-app.yaml.
It comes with the users, groups, and roles subapps.
The public folder in the users subapp is installed and configured by the Public User Registration module.
|
Only users assigned the superuser role have permission to access the subapps.
Workspaces
The subapps operate on the following workspaces:
| Subapp | Workspace |
|---|---|
|
|
|
|
|
|
Node types
The Security app module registers the following custom node types in the subapp configurations.
The subapps operate on these nodes types and on mgnl:folder.
| Subapp | Node type |
|---|---|
|
|
|
|
|
|
