User Access & Authentication

Drupal 8 Status: Stable, not feature complete.

In general, this module provides features that allow an IP address (or range of IP addresses) to be whitelisted which restrict the functionality of users. Currently there are two features implemented:

NOTE: This module is deprecated in favor of Auto Assign Role, which can be configured to provide the same functionality (and much more)

• Auto Assign Role Module

Allows the user to add a fifth component on the user registration URL containing a comma-separated list of roles to be automatically assigned to the newly-created user.

For example:

This module provides catalog and user integration with the Zen Cart e-Commerce package. It is not yet ready for public consumption and is intended for developers who wish to help with testing and patching the module. A good working knowledge of Zen Cart and Drupal development and administration is highly recommended to use this module.

Bug reports and especially patches are extremely welcomed.

User Permissions provides an interface for giving additional permissions to individual users without the need to assign them to a special role. When this module is enabled, users with the 'administer permissions' permission can access the 'User Permissions' tab on each user's account.

Donations

If you found this module useful, please consider making a donation via PayPal.

Redirect to a specified page after an administrator creates a user, based on the newly-created-user's roles.

This module depends on a new additional hook_user $op, after_insert, which must be manually added to Drupal core. Apply the following patch:

Multisite Login allows a user to login to all sites in a multisite configuration, even though the multisites do not share domain names.

For example:
  politicker.com
  politickernj.com
  politickerny.com
  etc.

NOTE: if you are using several sites on the same domain (ex. politicker.com, nj.politicker.com, ny.politicker.com, etc.), then you do not need this module. The multisite functionality in Drupal core has the ability to share logins for sites like these without additional modules.

This module was designed to be an alternative to the singlesignon module but using a technique that does not block search engines from accessing your websites.

This module implements the OAuth 1.0 standard for use with Drupal and acts as a support module for other modules that wish to use OAuth.

For OAuth 2.0, install the Oauth 2.0 module instead of this one.

This module is to provide an XMPP server for Drupal, including integration with, and authentication against, Drupal's own user account system.

Formerly part of the Devel module package, Devel Node Access (DNA) displays information related to the node access mechanism of your Drupal installation.

The {node_access} table and functionality are part of Drupal core, but they lie dormant until you install one or more node access modules that supply entries into the {node_access} table. Each node access module provides different strategies for controlling what each user can do with your nodes.

DNA has three audiences:

• It helps Drupal admins understand what is happening on their site, visualize how node access modules interact, verify that their customizations give the intended results, and finally answer the famous question: Why does this user have access to that node?
• It helps module and website support diagnose issues with node access on remote sites by instructing their clients to post screenshots and/or cut&paste listings of DNA output.
• It helps node access module developers implement and test proper behavior of their modules.

DNA is a tool for module and site development; it is not intended to run continuously on production sites, and its output is of no interest to website visitors, but if you run any node access module, DNA will help you with your work.