Access control modules and Drupal 11

Add challenge-response tests to user-facing forms on your site to protect against spambot submissions. Further CAPTCHA types are supported via contrib modules.

Provides a generic service for logging in and registering users that are authenticated against an external site or service and storing the authentication details.

The Field Permissions module allows site administrators to set field-level permissions to edit, view and create fields on any entity. Features Enable field permissions on any entity, not just nodes. Role-based field permissions allowing different viewing patterned based on what access the user has. Author-level permissions allow viewing and editing of fields based on who the entity owner is.

Provides a GDPR cookie banner where you can gather consent from the user when the website stores cookies on their computer or otherwise handles their personal information.

Allows site administrators (or anyone with enough permissions) to switch users and surf the site as that user

Gives users with specific roles the ability to view unpublished content of certain content types.

This module supports enforcing restrictions on user passwords by defining password policies. Overview A password policy can be defined with a set of constraints which must be met before a user password change will be accepted. Each constraint has a parameter allowing for the minimum number of valid conditions which must be met before the constraint is satisfied.

This module allows site administrators to grant specific roles the authority to assign selected roles to users, without them needing the administer permissions permission. For each role, Role Delegation provides a new assign ROLE role permission to allow the assignment of that role. The module also adds an assign all roles permission.

Easily configure Google reCAPTCHA v3 with a fallback challenge for enhanced security and user-friendly protection on your website.

The Override Node Options module allows permissions to be set to each field within the Authoring information and Publishing options field sets on the node form. It also allows selected field sets to be set as collapsed and / or collapsible.

The Profile module provides configurable user profiles. Comparison to user account fields Why use profiles instead of user account fields? With profile, user account settings and user profiles are conceptually different things, e.g. with the “Profile” module enabled users get two separate menu links “My account” and “My profile”.

The OpenID Connect module provides a pluggable client implementation for the OpenID Connect protocol. The server implementation of the protocol is provided by Simple OAuth (OAuth2) & OpenID Connect or the OAuth2 Server modules. What is OpenID Connect? http://openid.net/connect : OpenID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol.

This module provide single sign-on capability for your Drupal site by implementing the CAS protocol . When using this module, local Drupal user accounts are still used, but the authentication process is not handled by Drupal's standard login form. Instead, users are redirected to your institution's CAS server to collect credentials.

Content Access allows you to manage permissions for content types by role and author. It allows you to specify custom view, edit and delete permissions for each content type. Optionally you can enable per content access settings, so you can customize the access for each content node.

Redirect the HTTP 403 error page to the Drupal /user/login page with an optional message that reads: "Access denied! You must login to view this page." Also, the desired page is appended in the url query string so that, once login is successful, the user is taken directly where they were originally trying to go.

Allow users to register using an email address. Users can then log-in using their email address and password for authentication. This module aims to solve some usability issues in managing accounts on a Drupal site. On many sites the idea of a "username" is not necessary while the email is necessary.

Simple OAuth is an implementation of the OAuth 2.0 Authorization Framework RFC . Based on League\OAuth2 This module uses the fantastic PHP library OAuth 2.0 Server from The League of Extraordinary Packages . This library has become the de-facto standard for modern PHP applications and is thoroughly tested. Recommendation Check the official documentation on the Bearer Token Usage .

ECA is a visual automation and orchestration framework for Drupal. ECA enables users to model workflows, business rules, approvals, content behavior, integrations, and AI-powered processes without writing custom code. ECA lets you automate how your Drupal site behaves through a visual workflow builder.

This module allows site builders to set up fine-grained permissions for allowing "sub-admin" users to manage other users based on the target user\'s role. The module defines new permissions to control access to edit/delete users - more specific than Drupal Core\'s all-or-nothing 'administer users'.

The Group module allows you to create arbitrary collections of your content and users on your site and grant access control permissions on those collections Out of the box, Drupal only allows a person to view, create or edit the different content types you create. However, you might want to be able to let them view or edit all content types, but only in a specific section of the site.

What Is Username Enumeration Prevention By default Drupal is very secure (especially Drupal 7). However, there is a way to exploit the system by using a technique called username enumeration. Both Drupal 6 and 7 have this issue, but it is much worse for people using Drupal 6. This is because Drupal 6 does not have any built in brute force prevention.

Allows users to authenticate against a SAML Identity Provider to log in to your Drupal site.

This simple Drupal module allows users to log in with either their username OR email address from the same input box on the standard login form (it turns the "name" field into a username OR email address field). REQUIREMENTS Core dependencies only.

This module allows fine-grained access control of user administrators, by providing various editing protection for users. The protections can be specific to a user, or applied to all users in a role. Note: Up until the D7 version, User Protect has a complicated configuration -- please take the time to read the very extensive module help before using it! Provided protections The following

Now part of Drupal core 10.3 as the Access Policy API This module has been turned into a core system: #3371246: [Meta, Plan] Pitch-Burgh: Policy based access in core Please do not start a new project using this module, unless you are using Group v2 or v3. A v2.0.0 release will come out to bridge the gap between old code (this module) and new code (Drupal core 10.3).

Two-factor authentication for Drupal sites. Drupal provides authentication via something you know -- a username and password while TFA module adds a second step of authentication with a check for something you have -- such as a code sent to (or generated by) your mobile phone. TFA is a base module for providing two-factor authentication for your Drupal site.

Features Block concurrent editing: When a user is editing a node, any other user that attempts to edit the same node will be blocked from doing so, and notified that the content is already being edited. By node type: This module can be configured to only lock certain content types against concurrent editing.

RoleAssign specifically allows site administrators to further delegate the task of managing user's roles while withholding the Administer permissions permission. RoleAssign introduces a new permission called Assign roles . Users with this permission are able to assign selected roles to still other users.

Lightweight Directory Access Protocol (LDAP) lets you: Login with LDAP credentials Single-Sign On available through 3rd party modules Provisioning from LDAP to Drupal Provisioning from Drupal to LDAP Setup Guide LDAP Server Defines how to communicate with the domain.

Module description Protected Pages modules allows the administrator to secure any page by password. Visit module configuration page and add path + password. After that the added path will be password protected. This module also allows you to send the details of this protected page to multiple users by email.

The RealName module allows the administrator to choose fields from the user profile that will be used to add a "real name" element (method) to a user object. Hook_user is used to automatically add this to any user object that is loaded. It will also optionally set all nodes and comments to show this name.

This module enables users to login by email address with the minimal configurations. For configuring mail login go to "/admin/config/people/mail-login". Available configurations: Enable login by email address: This option enables login by email address. Override login form: This option allows you to override the login form username title/description.

Menu Item Role Access allows you to restrict to the menu items users see without having completely separate menus, controlling access all based on user role.

Description: This is an easy to use module that grants access to view unpublished content (node, media, anything that implements EntityPublishedInterface) to anyone who has a unique URL and appropriate permissions. This module is useful for proofreaders, content checkers etc. Webmaster does not need to create user accounts and can keep the website safer.

This module integrates Drupal with SimpleSAMLphp , the most robust and complete implementation of SAML in PHP. It makes it possible for Drupal to communicate with SAML or Shibboleth identity providers (IdP) for authenticating users. The resulting Drupal site can effectively act as a SAML or Shibboleth service provider (SP).

This module is here to alleviate frustration when trying to manage permissions in Drupal. By providing a better permissions interface hopefully a few innocent keyboards and mice can be saved. Branches 4.0.x : Drupal 9, 10 & 11. 3.0.x : Drupal 8+9 (no longer recommended).

SUMMARY - Redirect After Login ================================= A simple module providing a feature to redirect users according to an URL-defined the parameter after logging in. Allows redirecting only the internal URL of the site. CONFIGURATION ------------------- 1.

The Domain project is a suite of modules that provide tools for running a group of affiliated sites from one Drupal installation and a single shared database. Drupal 10/11 status Releases in the 2.x and 3.x series are compatible with Drupal 10.2 and higher. The 2.0.x branch is considered feature complete and will receive bug fixes only.

User consent management module for Drupal. The module enables existing third-party-integration modules continued to be used in compliance with the GDPR (of course without manipulating their code). It solves the basic problem that when using third-party-integration modules, the user must agree to the use of cookies (according to GDPR) before they are installed.

Remove "Request new password" link from block and user page. This module is very useful for sandbox sites where test users can't change your own password and for third party authentication like LDAP. Configuration Once installed and enabled then configure the options at "admin/config/people/noreqnewpass" - you will get checkbox 'Disable Request new password link' .

As of Drupal 10.1.x-dev, this module is no longer needed and the "Block Content" core module's permissions can be used instead. See migration notes below. There are no plans to support Drupal 11+. The Block Content Permissions module allows you to control access to administer block content types (custom block types), administer block content (custom block library), and create, update, or delete

The LoginToboggan module offers several modifications of the Drupal login system in an external module by offering the following features and usability improvements: Allow users to login using either their username OR their e-mail address. Allow users to login immediately. Provide a login form on Access Denied pages for non-logged-in (anonymous) users.

The Block Region Permissions module allows you to control access to administer blocks within each theme's regions. The following permissions are added: Administer: [ theme ] - [ region ] Grants access to manage a theme's region: View region's header, message, and blocks on block layout page View region in region selector fields on block layout page View region in region selector field on

This very light-weight module allows additional permissions to be created and managed through a administration form. It uses the menu access system to allow or disallow access to it. On the administration page a user is able to create a permission with name and path(s). These permissions can then be assigned to roles on the permissions page.