User Access & Authentication

Swipht technologies developed a set of security modules with sponsorship from Portland State University. The modules provide roles and user specific security permissions for menus, menu items, nodes, and security integration into the administration and help systems. We would like to provide this suite of modules back to the community to share the usefulness of the suite and involve the community to provide additional support, testing, and moderation.

Swipht technologies developed a set of security modules with sponsorship from Portland State University. The modules provide roles and user specific security permissions for menus, menu items, nodes, and security integration into the administration and help systems. We would like to provide this suite of modules back to the community to share the usefulness of the suite and involve the community to provide additional support, testing, and moderation.

Project abandoned.

This module is still in the early development phase - nothing much to see here yet. If you're not sure what CAS (Central Authentication Service) is, this module probably isn't for you.

This module allows a Drupal instance to restrict registration to those who can successfully authenticate via CAS (as configured by the site admin). Unlike the CAS module, which creates a Drupal user account or logs into an existing Drupal user account when an individual authenticates via CAS, this module does not interface with Drupal's user authentication system. Instead, it sends an invitation via email (in the same manner that the Invite module does) to register on the Drupal site (like normal) to users who successfully authenticate via CAS. In this way, CAS is used as part of the registration process, but not to log in.

Read the README.txt before installing. An external library (phpCAS) and specific PHP modules (curl, openssl, dom, zlib) are required.

Desktop Notify provides some preset update notifications to desktop applications. This version was specifically created for the Drupal Notifier application.

See a screencast here: http://myzonelabs.com/notifier-app

I expect the current 6.x-1.x-dev module to work finely on Drupal 5. If it doesn't, let me know.

This module provides single sign-in and user database integration for MediaWiki as slave of Drupal. It is set up so that users sign in to the Drupal site, and as a result they automatically become logged in to the wiki. User entries are still created in the wiki's user table and are kept up to date on each login with email and real name. This does not include content exchange or wiki parsing, for that, see the Mediawiki module.

Module allows automatic registration of (successfully logged in) OpenID users, even in case OpenID provider didn't supply data necessary for Drupal user registration (valid username and email).

Module maintained by Valery Lourie (http://www.valthebald.net)

This module has been superseded by Permissions Grid, which handles all structured permissions rather than just nodes.

This gives an alternative way of administering node-related permissions which may be easier on sites with many content types and roles.

For each role, a grid of permissions is shown, where each row is a content type (grouped by module) and each column is an action ('create', 'edit own', etc).

This module integrates rules with browscap, to allow for conditional actions based on the browser that is being used.

Here is a comparison of similar modules.

Description

Enabling this module will disable the password strength checker upon new user registration. This is for sites that find the strength checker unnecessary, annoying or confusing to users.

Current Maintainer

Jaime Herencia (Web Partners)

Sponsorship

Completely rewrite of the 7.x branch sponsored by Web Partners

This simple modules aims at linking group members and nodes via taxonomy.

A goup member is only granted access to a node if her group matches has at least a common taxonomy term with the node.

Taxonomy is often used to define hierarchy in organic groups. This module allows to restrict node access for groups within those taxonomy vocabularies.

Example: