User Management

LDAP provisioning module provides a user registration process with an optional account approval queue in Drupal and creates user accounts in both LDAP server and Drupal.

It depends on the ldapauth module in the http://drupal.org/project/ldap_integration package.

This project is being developed by Miglius Alaburda.

Developed by OpenBand, an M.C. Dean, Inc. company.

Security: This module is considered insecure by Drupal security team and all of it's releases have been unpublished. You are strongly encouraged to disable the module on your site.

Quota by role is a module that confines certain roles to defined quotas by content type.

Allow users to register and login using only an email address. Users can then log-in using their email address and password for authentication.

User Profile Theme allows user to have a different CSS only theme for their profile page.

Each user who is allowed to have a theme (using roles) gets a new field in his profile edit page. There he is allowed to put some CSS which is applied only to his profile page using an external CSS file

This module still needs some development but is already usable.

So, you have a usernode. Do you want to make further sense of it? ;)

Having a user a node gives also the possibility to post comments on a user. Let's use these comments as guestbook entries!

usernode_guestbook is another way of implementing a guestbook functionality besides the former guestbook module. If you want a guestbook that behaves in a different way to usual comments and you don't have usernode module installed, use guestbook. But if you have installed usernode already in order to display users in views module, and you want your guestbook entries to look and to behave in the very same way as usual comments do, then you should consider to choose this module.

The Courier MTA module gives administrators and/or users the ability of managing e-mail accounts for a Courier mail server through a Drupal website.

Expires rows from the session table older than a certain time.

Background

By default, Drupal ships with a session expiration time of just over 23 days, using this directive in settings.php:

ini_set('session.cookie_lifetime',  2000000);

However, for this to work automatically, it requires PHP's garbage collection to be configured correctly.

Since some distributions, e.g. Debian and Ubuntu do not ship with PHP defaults that triggers PHP garbage collection, there is a need to also set the following:

ini_set('session.gc_probability', 1);
ini_set('session.gc_divisor', 100);

This will work, but has some drawbacks:

• It will be triggered at some random time, rather than at a predictable time.
• It could slow the response for the unlucky user who happens to trigger it.

So, on sites with a distribution that is not setup as above, or on really busy sites, the sessions table can grow to be very large, and that can cause slow accesses to it, as well as slow writes due to locking, leading to performance bottlenecks.

Single Login is a session management system for Drupal. It allows the site administrator to create a policy to detect, and prevent, duplicate logins on the same account. This is obviously handy for a site that requires paid subscriptions. Once a duplicate login is detected from a different system, the first login gets logged out. The admin can set a policy that determines how often and within what time period a session can "ping pong" between machines. Should the policy conditions be met, the admin can specify an action,typically to block the offending account.

The Role Contact module creates a "staff list" from the profiles of users in a particular role, e.g. "staff role". The user list is formatted via theme functions, with convenient header and footer fields. The sort order of users can be set via weights. A configurable subset of profile data is shown in the user list view, along with the user's picture along with a link to a per-user page, showing a (potentially different) subset of profile data.

The PAM Auth module is based vaguely on a skeleton of the IMAP Auth module (http://drupal.org/project/imap_auth). It accomplishes the same goal except that it uses the PHP5-PAM module to accomplish the authentication. It also borrows some ideas from the ldap_integration (http://drupal.org/node/15109) module for password-form adjustments.