Modules: User access/authentication

Account reminder

Account reminder is a simple module that will resend the welcome email to users who have registered with the site but have not yet logged in. The admin can control the initial time before sending a reminder, the time period between subsequent reminders and the total number of reminders to send. The email that is sent is also fully customizable.

Version	Date	Links	Status
6.x-1.1	2008-Oct-09	Download · Release notes	Recommended for 6.x
5.x-1.0	2008-Jun-19	Download · Release notes	Recommended for 5.x

ACL

The ACL module is an API for other modules to create lists of users and give them access to nodes. It has no UI of its own and will not do anything by itself; install this module only if some other module tells you to.

I'm aware of the following modules using ACL (let me know if you know of others):

• Content Access (uses ACL to provide by-user access control, if it's installed)
• Forum Access
• Image Gallery Access

We now have BETA3 for Drupal 6 — please test it and provide feedback (both good and bad!) in the issues queue. See #322279: BETA3 for D6 for details.

Version	Date	Links	Status
6.x-1.0-beta3	2009-Jan-03	Download · Release notes	Recommended for 6.x
5.x-1.6	2008-Mar-12	Download · Release notes	Recommended for 5.x

Administer Users by Role

Allows users with 'administer users' permission and a role (specified in 'Access control') to edit and/or delete other users with a specified role.

If the user being edited has multiple roles, the user doing the editing must have permission to edit ALL of the user being edited's roles.

Also provides role-based control over user creation.

Works well in conjunction with the (optional) role_delegation module.

I wrote this module as part of a Kosada Inc development project --- this allows us to further delegate user administration. Site administrators can now create users without being given full "administer users" permission, and can edit a specified subset of the site's users depending on the combination of roles possessed by the editing user and the user being edited.

Version	Date	Links	Status
5.x-0.9	2008-Mar-16	Download · Release notes	Recommended for 5.x

Alternate Login

This module provides a simple interface that allows registered users to use a login name which is different than their username.

Version	Date	Links	Status
6.x-1.0	2008-Feb-16	Download · Release notes	Recommended for 6.x
5.x-1.8	2007-Dec-29	Download · Release notes	Recommended for 5.x

Apply for role

Allows users to apply for a role and administrators to approve their application. The role will be automatically assigned to the user on approval.

Version	Date	Links	Status
6.x-1.8	2008-Dec-20	Download · Release notes	Recommended for 6.x
5.x-1.4	2008-Jun-29	Download · Release notes	Recommended for 5.x

Auto username

This module disables the "Username" field on user registration and user edit forms and generates a username automatically using a token.module-provided pattern. That allows for usernames that are, for instance, forced to be "Lastname, Firstname", "Firstname Last-initial", etc.

auto_username depends on token.module.

Status

There is one show-stopper bug in the 5.x-1.x-dev release: #254422: Using old data for tokens. A stable release of this module will be tagged after that has been fixed (and hopefully any other bugs, too). If you want to see a stable release, please fix that bug! :-)

Version	Date	Links	Status
5.x-1.x-dev	2008-Apr-15	Download · Release notes	Development snapshot

Autologin

Autologin enables a smooth login method by means of using account credentials in the URL. Simply enable the module and go to login/<username>/<password> and you will be logged in. If Login Destination is installed, Autologin will use its settings. While this module is not recommended for your everyday site, it comes much in handy for sites with (preferrably) limited user accounts, where ease of participation is of high concern.

Note from the security team: This exposes the login credentials via the URL, so it's visible in the access log of the site and potentially other places a user wouldn't want their password to be seen in plain text. Only use this module on test sites where you don't care about your password being compromised.

Version	Date	Links	Status
6.x-1.0	2008-Dec-22	Download · Release notes	Recommended for 6.x

Book access

This module allows access control for Drupal books on a per-book basis.

You may configure role-based view, edit and delete permissions for each individual book. Those permissions will be applied to all child book nodes (aka "book pages"). This module does not allow per-node permission settings.

This module is based loosely on the forum_access module.

Module development sponsored by:

• LifeWire
• WorkHabit

Version	Date	Links	Status
6.x-1.0-rc1	2008-Sep-13	Download · Release notes	Recommended for 6.x
5.x-1.0	2008-Jan-29	Download · Release notes	Recommended for 5.x

CCK groups

CCK groups provides a minimal set of groups functionality using CCK features.

Emphasis on minimal approach, anyone wanting a full groups solution should use Organic Groups (og) instead.

Example Use:

Limit access to a Case Tracker project and its cases to selected individuals.

Version	Date	Links	Status
5.x-1.x-dev	2008-Apr-25	Download · Release notes	Development snapshot

CiviCRM Active User

civicrm_activeuser is a simple module that adds a user to a group upon Drupal login.

This was developed primarily to support a double-optin check when using CiviMail. Not only must the user signup for a CiviCRM group, they must use their Drupal login by signing in at least once.

See also CiviCRM Subscribe

Version	Date	Links	Status
6.x-1.x-dev	2008-Apr-28	Download · Release notes	Development snapshot
5.x-1.2	2008-Feb-19	Download · Release notes	Recommended for 5.x
4.7.x-1.0	2006-Dec-08	Download · Release notes	Recommended for 4.7.x

CiviRoles Sync

11-19-2008 - THIS MODULE IS NO LONGER BEING MAINTAINED ON DRUPAL.ORG, THE FILES BELOW ARE FOR LEGACY/ARCHIVE PURPOSES ONLY.

Sorry for the late update, but there were some exciting developments with this module last month. The CiviCRM Core development team has been working on migrating this module into the main distribution of the CiviCRM module and will be maintaining it there. I have been told via e-mail that we can expect to see the CiviMembers/Drupal Roles sync features as early as CiviCRM v2.1.2, which should be available soon. The modules below will no longer be maintained here and any support questions should be asked on the CiviCRM Forums (http://forum.civicrm.org/) when v2.1.2 goes public. I would like to thank everyone who supported me in developing this module and for Matt2000's contributions. I'm sure these features will be very exciting in future releases of CiviCRM.

For more information please see this CiviCRM developer blog posting: http://civicrm.org/node/464

-- Neil Goodman (aka posco)

Module Description:

CiviMember Roles Sync automatically synchronizes CiviCRM Contacts that have CiviMember Membership Types to a specified Drupal Role. This allows sites that use Drupal and CiviCRM to create membership sites with "member-only" content.

Version	Date	Links	Status
6.x-3.0-beta1	2008-Sep-01	Download · Release notes	Recommended for 6.x
5.x-2.0	2008-Aug-02	Download · Release notes	Recommended for 5.x

Content Type Administration by Organic Group

Currently being developed and maintainted by Paul Booker @ Glaxstar.
Many thanks to Glaxstar for their continued support of Drupal projects.

UPDATE: As of the 18th December Glaxstar will only be supporting the Drupal6 version of this module. Please upgrade to the latest version.

Since the permission system only lets the admin allow/disallow creation of content types and can't specify WHERE they can be used, this module tries to solve that problem. This module allows the admin to limit content types available site-wide and by group. Group owners can then choose which types to use within their group. Group owners can use ALL content types ALLOWED to that group, even if that owner only ACTIVATES a subset of those types for use by his members. All regular permissions and roles are still valid and this module will not override your settings there. So, given that a user has permission to create a content type SOMEWHERE, this module will limit where exactly they can do that. You can limit or even forbid creation of content at the site level, at the overall group level, or at individual groups.

Version	Date	Links	Status
6.x-1.0-beta1	2008-Nov-12	Download · Release notes	Recommended for 6.x
5.x-1.6	2008-Sep-03	Download · Release notes	Recommended for 5.x

COPPA

This module will prevent users under the age of 13 from logging in if their respective parent or guardian (P/G) have not "signed" their COPPA compliance form. If a users Date of Birth -- stored in their user profile -- cannot be determined, the user will not be allowed to login.

P/G to child relationships will be loaded into an internal {coppa} table. This table will track the Parent to Child relationships and monitor when COPPA compliance was first achieved.

Suggested setup;

1. enable profile module
2. enable coppa module: this looks for a profile field called "Date of Birth" (profile_dob) and creates it if not present.
3. create a user role that will require COPPA compliance suggestions (student, etc.)
4. visit 'admin/settings/coppa' and select the above user role
5. also visit 'admin/user/coppa/add' to add parent/child relationships
6. also visit 'admin/user/coppa/manage' to manage existing parent/child relationships

Any users with the role you select at 'admin/settings/coppa' will now require coppa compliance to login and use the site. Please be careful in choosing the role; using "authenticated user" can lock all users out of the system if they do not have a profile_dob over 13 years from the current date.

Version	Date	Links	Status
5.x-1.2	2008-Jul-29	Download · Release notes	Recommended for 5.x

Create quota

Create quota module creates quota rules and holds information about every user's creation count.
A possible use case for this module is a site that allows users to register for free and to create a certain amount of content until they are asked to pay for the service.

Version	Date	Links	Status
6.x-1.x-dev	2008-Dec-07	Download · Release notes	Development snapshot

Custom username validation

For a customer, i needed to validate the username against a german phone number, so i wrote this little module that allows to define a validation pattern for the username on registration. it's also possible to customize the error message on validation failure.

Version	Date	Links	Status
5.x-1.0	2008-Nov-22	Download · Release notes	Recommended for 5.x

Domain User Default

The Domain User Default module is a submodule for the Domain Access module that provides methods for users (and unauthenticated site visitors using the Session API module) to select a default domain. The module can be configured to automatically redirect users to their default domain upon visiting another domain, or simple provide a message when they are on another domain.

This module provides integration with the Domain GeoLocalization which allows users to search for domains within a given proximity.

Required modules

• Domain Access

Optional modules

• Domain Geolocalization
• Session API

The Domain User Default module is sponsored by One Economy, and developed and maintained by OpenSourcery.

Version	Date	Links	Status
6.x-1.0	2008-Oct-03	Download · Release notes	Recommended for 6.x

Drupal vB

Drupal vB integrates vBulletin forums with Drupal. It allows

• existing vBulletin users to log in to Drupal
• new vBulletin users to log in to Drupal
• existing Drupal users to log in to vBulletin (after initial export)
• new Drupal users to log in to vBulletin
• a single/shared sign-on when logging in via Drupal
• updating user data in vBulletin upon update in Drupal
• deleting users in vBulletin upon deletion in Drupal

Unlike vbDrupal (a fork of Drupal), Drupal vB turns Drupal's user-base into the primary user-base (while still allowing existing and new vBulletin users to logon with their user credentials in Drupal) and does not require patches to Drupal core.

Drupal vB currently ships with 3 blocks:

• Recent threads/posts
• Forum users/posts/pm statistics for the current user
• Overall forum statistics (administrative)

Major parts of Drupal vB are based on my work for Migrator module. If you rather want to migrate an existing forum to Drupal (instead of integrating it), you might want to checkout Migrator.

Version	Date	Links	Status
6.x-2.0	2008-Oct-18	Download · Release notes	Recommended for 6.x
5.x-2.2	2008-Oct-15	Download · Release notes	Recommended for 5.x

E-Journal

This module is a powerful production publishing system. It allows you to create and control your own electronic (and possibly printed) journals in Drupal - you can set up as many journals as you want, add authors and editors. Module gives you issue management, basic user and access control, vocabularies and archives. This module was inspired by Open Journal System which is an open-source online submission and manuscript tracking system. The Drupal platform is more flexible though, it gives you many ways to extend your publishing system.
Currently, the module is made of the following packages (needless to say, you can combine them with other modules):
ejournal - the core functionality of an publications/issue management
ejournalaccess - for setting access to different group of users
ejournalauthors - use Drupal taxonomy as user profiles links
ejournalcitation - construct citation reference beneath published articles
ejournalshortly - for publication of short messages along side with the main content

Version	Date	Links	Status
6.x-1.0-alpha2	2008-Dec-21	Download · Release notes	Recommended for 6.x
5.x-2.0-rc3	2008-Dec-21	Download · Release notes	Recommended for 5.x

Edit Authoring Information

This tiny module adds more granular permissions in order to let users edit a node's Authored by and/or Authored on field (without them being granted the all-powerful administer nodes permission).

Version	Date	Links	Status
5.x-1.0	2007-Sep-09	Download · Release notes	Recommended for 5.x
4.7.x-1.0	2007-Sep-09	Download · Release notes	Recommended for 4.7.x

Email Verification

This module provides advanced email address checking. The core of Drupal, through the user module, only performs syntactical checking of user-entered email addresses, both during registration and account edition. This creates loads of problems when users incorrectly enter their address. First, they don't get any email from the site. If it happened during registration, they will not get their password. They will either bug the site admin or give up on the site altogether, both cases being a bad thing. Second, the site admin will get email bounces, which soon gets annoying if you have a moderately busy site.

This module tries to solve this problem by checking that the address really exists when it is entered by the user. First, it checks if the domain/host part exists at all, and reports an error if it does not. I found that this step alone catches between 1/2 and 2/3 of typos. Second, it tries to validate the user name too, by sending a HELO/MAIL FROM/RCPT TO chain of commands to the SMTP servers for the found host. Some hosts will not reveal if the user name is valid ("catch-all policy") while others might refuse the check for some reason (for instance, some hosts refuse deliveries from IPs delivered to home users by Internet access providers). When in doub, we try to play it safe and rather accept some invalid addresses than to refuse valid ones.

Version	Date	Links	Status
5.x-2.0	2007-Jun-23	Download · Release notes	Recommended for 5.x
4.7.x-1.0	2007-Jan-07	Download · Release notes	Recommended for 4.7.x

FUDforum integration

This module provides integration with FUDforum (a popular PHP forum system like phpBB). The following (all optional) blocks are provided to integrate your forum with your drupal site:

Version	Date	Links	Status
6.x-1.0	2008-Dec-28	Download · Release notes	Recommended for 6.x
5.x-1.1	2007-Sep-15	Download · Release notes	Recommended for 5.x
4.7.x-1.x-dev	2006-Nov-13	Download · Release notes	Development snapshot

Hidden

"Open Publishing" sites require transparency of the "open editing" process.

This module creates a way of removing nodes and comments from the main site, but keeping them accessible to users in a special location with an explanation of the editorial reasons for "hiding".

Features include:

• Hidden articles are always displayed with the reason that they are hidden, and custom css class.
• The reason for hiding can be selected from a list or/and typed in.
• All pages with /hidden have robots meta tags to ask for no indexing.
• Filters can be set to automatically hide posted nodes and comments, this can be obfuscated with delay.
• Notification of hidden articles can automatically be sent out by e-mail. This can be individually or in batches.
• Non-admin users can be encouraged to take part in editorial process by enabling the reporting of posts for hiding.
• This is not a node access module. Nodes and comments are indexed and unpublished.
• Views integration (Drupal 6 Views2 integration to do).

This module was developed for Indymedia Drupal sites and should be of use to any other sites that want to ensure transparency of editorial process.

Version	Date	Links	Status
6.x-1.x-dev	2008-Dec-19	Download · Release notes	Development snapshot
5.x-2.3	2008-Dec-18	Download · Release notes	Recommended for 5.x

Image Gallery Access

This module changes your image gallery administration page to allow you to set image galleries private. You can control what user roles can view, edit, delete and post to each gallery. You can also give each gallery a list of users who have administrative access on that gallery (AKA moderators).

Image galleries are provided by the Image Gallery module inside the Image module. Image Gallery Access also requires the