User Access & Authentication

SQL authentication is a module that uses the external authentication methods in Drupal to connect to any other database.

Whether that is a PHPbb MySQL database, or another drupal site in postgresql does not really matter. It is fully configurable and easy to use. Multiple hashing algorythms are supported too, configurable in the settings interface.

Its user-end system is similar to the drupalID, with one difference: your data will not go unencrypted over the big bad web.

This node_access module governs access to nodes based on the taxonomy terms applied to the nodes. A simple scheme based on taxonomy, roles and users controls which content is visible.

The Node Access Arbitrator is an experimental module API designed to allow multiple node access systems to work together.

Currently it is 4 modules

Fostering a relationship of trust with your visitors is essential when you aim to collect personal information and provide a service with which they feel secure. With this familiar little feature added to your installation you will portray the message of making every effort to address your users' security concerns and put them at ease. It shows that you stop at nothing to go the extra mile and allow them the peace of mind, to access your site with confidence from anywhere in the world knowing that you have taken every precaution to ensure their identity is safe.

This module provides Drupal user authentication using an IMAP, POP, or NNTP server as the backend. The site administrator can choose which servers can be used for authentication, or enable all servers.

The module maintains Apache access control files (.htpasswd). User name/password is taken from Drupal user database.
Users are listed according role.

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)

Under pacs, every drupal node turns in a container wich can hold normal content but also other nodes of any type, much like a directory in an apache web server. You can control the access permissions on each of the nodes for each single defined user role. Nodes with no explicit permission settings inherit them from its parent node, like in a directory tree.

The Login Destination module allows you to customize the destination that a user is redirected to after logging in, registering to the site (7.x), using a one-time login link or logging out (7.x). The destination can be an internal page or an external URL. It is possible to specify certain conditions like referring pages or user roles and make the destination depend upon them. You may use PHP snippets to provide custom conditions and destinations. It is also possible to keep users on the currently visited page after logging in or out.

The 4.7-1.0 version was originally developed by JanRain to implement OpenID consumer support in Drupal using the JanRain PHP OpenID and Yadis libraries. The 4.7-2.x branch was developed by James Walker and Rowan Kerr to support OpenID 2.x, and include a server and a client component.