Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Types of users


Type

Example

Image Added

Users

Accounts for people who work on site content such as authors, editors and publishers.

Image Added

System users

Technical accounts such as superuser and anonymous .

Image Added

Public users

End users or visitors of the site. They can be registered through the Public User Registration (PUR) module. Registering visitors allows you to provide them with personalized content such as members-only sections of the site, newsletters and mailing lists.

superuser

Multiexcerpt
MultiExcerptNamesuperuser-user

The term superuser may refer either to a system user (an account type) or to a role (a definition of what a user is allowed to do in the system). In a vanilla installation of Magnolia, the superuser role is assigned to the superuser account. In addition to the superuser role, the superuser account has some other roles too, see Default roles, groups and users.

As the name implies, the permissions of the superuser account are usually unrestricted in any way. For instance, superuser can read and write to all default JCR workspaces on / .

Bestpractice

On a production system, create specific users with distinct roles and deactivate the superuser account.

anonymous

Multiexcerpt
MultiExcerptNameanonymous-user

The term anonymous may refer either to a system user or to a role. The latter is assigned to the former. Apart from the anonymous role, the anonymous system user is by default assigned other roles too, see Default roles, groups and users.

Every Magnolia resource intended to be accessible without authentication must be enabled for the anonymous system user. A users that interacts with Magnolia without authentication is determined as anonymous user.

Multiexcerpt
MultiExcerptNameanonymous-role-do-not-activate
Note

On most systems, the rights and permissions of the anonymous role differ between author and public instances: allow read access to all on the public instance, while deny the same on the author instance. That is why you should not activate that role.


Anchor
edit-user-preferences
edit-user-preferences

Editing user preferences

A logged-in user can set one's own preferences by clicking the Edit user profile action in the top right corner. To access the action, click the down arrow in the corner:

Image Added

The action opens a dialog whose User profile tab allows changing the user's password, full name and email address:

Image Added

Use the dialog's Preferences tab to edit the user's language and the time zone.

Image Added

Anchor
setting-user-timezone
setting-user-timezone

Setting the user time zone

Every user can set one's own preferred time zone. Open the user preferences dialog, click the Preferences tab and set the time zone accordingly.

Image Added

Magnolia continues to record events such as page creation using the host server time. The recorded time is converted and displayed in the user's preferred time zone.

Image Added

Anchor
organizing-users
organizing-users

Organizing users

In Magnolia, users are organized as follows:

  • Users can have both roles and groups.
  • Groups can have groups and roles.
  • Roles can have only Access Control Lists (ACLs). 

Image Added

Permissions are defined in the ACL. Users inherit permissions from the roles and groups assigned to them.

In a small site you can manage users and groups in Magnolia. On a larger site (hundreds of users), it is better to manage users and groups in an enterprise-grade user management infrastructure such as Microsoft Active Directory. You would define roles and ACLs in Magnolia but manage users and groups in the external system.

Tip

Get a list of all permissions assigned to a user or group in the Tools tab of the Security app.

Anchor
editing-user-permissions
editing-user-permissions

Editing user permissions

Every user known to Magnolia is granted a set of permissions defined by roles. You can either assign roles directly to a user, or assign a user to a group that itself grants a set of roles (see organizing users above).

Use the Security app to edit the permissions. The app is available in the Set up group of the AdminCentral and by default the superuser role is required to access it.

Image Added

The Security app provides subapps to edit the users (system users and public users), groups and roles. Select the user you want to edit and double-click it or use the Edit user action. The Edit user action is available in the following subapps: Users, System users and Public users.

Image Added

The dialog where you can edit user details has three tabs:

  • User info: Use this tab to edit the user's name and full name, the password, the email address, and the language, a property editable also in the user preferences dialog. You can use the tab to enable or disable a user account.
    Image Added
  • Groups: On this tab you can assign the user to existing groups:
    Image Added
  • Roles: On this tab you can grant roles to the user.
    Image Added

Automatic lockout

Automatic lockout is a security precaution that prevents users from accessing Magnolia after a number of failed login attempts.

Comment


By default, the lockout is triggered, and the account is automatically disabled by a minimum of N+1 failed login attempts. The number of failed attempts is configurable. When a non-existent username is entered lockout does not occur as the account does not exist. The lockout applies to system users and admin users but does not affect public users. After lockout, an administrator can re-enable the user account by checking the Enabled box in the user profile. When a lockout occurs, this checkbox is cleared.

Image Added

The number of failed login attempts N that will trigger lockout is configurable using the property maxFailedLoginAttempts at Configuration > /server/security/userManagers/system and /admin. Different values may be set for Users and Systems Users.

Advanced Tables - Table Plus
heading0
enableHeadingAttributesfalse
enableSortingfalse
classm5-configuration-tree
enableHighlightingfalse

Node name

Value

Mgnl f
server


Mgnl f
security


Mgnl n
userManagers


Mgnl n
system


Mgnl p
class

info.magnolia.cms.security.SystemUserManager

Mgnl p
lockTimePeriod

0

Mgnl p
maxFailedLoginAttempts

5

Mgnl p
realmName

system

Mgnl n
admin


Mgnl p
class

info.magnolia.cms.security.MgnlUserManager

Mgnl p
lockTimePeriod

0

Mgnl p
maxFailedLoginAttempts

5

Mgnl p
realmName

admin

Properties:

Multiexcerpt include
MultiExcerptNameUserManager properties
nopaneltrue
PageWithExcerptLDAP Connector module