User Access & Authentication

Fierce SSO is a Single Sign-On module for Drupal. It is designed so that if users log in to any one of your sites, it will automatically log them in to all the sites in the "network". It works by embedding special, invisible GIF images on the Welcome screen that users get after they log in. These images connect to the other sites in the network and silently log you in.

Fierce SSO is an alternative to danielc's singlesignon module (which does some magic by manipulating session tables in the background instead of using invisible images). I think my module uses a simpler approach and is more seamless to users. However, it occasionally fails if users have images turned off or if they navigate to another page after logging in without waiting for the page to finish loading.

For sites that are available via both HTTP and HTTPS, Secure Login module ensures that the user login and other forms are submitted securely via HTTPS, thus preventing passwords and other private user data from being transmitted in the clear.

Secure Login module locks down not just the user/login page but also any page containing the user login block, and any other forms that you configure to be secured.

This module makes it possible for users with a VCS account to associate Drupal nodes ("project nodes") with repository locations and appoint co-maintainers for these projects, which enables commit access control based on project maintainership.

Version Control / Project Node integration depends on the Version Control API and the Project modules.

OG User Roles allows group administrators of organic groups to grant additional user roles to individual members of a certain group.

Any additional permissions only apply within the context of this group and not globally. This means that the additional user roles to grant are determined and assigned by the requested page; e.g. node/123 belongs to group XYZ for which the user was granted additional roles. If the user goes to another page that does not belong to the same group, the additional user roles are no longer assigned.

Additional user roles can only be granted, not revoked.

Site administrators may also configure a default user role for new group members or a default user role for new group admins.

Should support most uses of facebook authentication.

If you are looking for developing a facebook app, you might be looking for the facebook api module (http://drupal.org/project/facebook_api).

Repeat, this will only let you login to a site using your facebook credentials, nothing else.

USE THE NEW 1.6 RELEASE - it should be stable and contains bug fixes. Looking for co-maintainer. See message in issue queue.

This module adds the ability to have several different membership types, each collecting different data from the user for registration by using custom content types and the combination of nodeprofile and pageroute modules (both required). The accounttypes module is recommended but not required. See each required module for any dependencies that they might have.

What this module does is:
When a user attempts to register for your site, they will first be presented with a drop down selector of membership types which you as admin have previously defined. They will read instructions for proper membership type selection that you previously wrote. After selecting and submitting this form, they will be presented with the standard Drupal registration form. Depending on whether you require admin approval of new accounts and/or email verification, the user will then either - a) be immediately presented with pageroute consisting of nodeprofile pages which will collect further data from them, b) be logged out so they can verify their email, then when they return be presented with the pageroute for their membership type as in (a), or c) after the admin has unblocked their account and/or the user has verified their email, when they return they will be presented with the pageroute as in (a).

In all cases, if you require that certain pages of the pageroute be filled out before the user can use the site, they will be routed to the next unfilled page at each login, or each attempt to browse to another page until they do. In other words, they will be stuck until they complete registration, except that they can logout at any time.

See the USAGE example in the README for how to setup nodeprofile, pageroute, and your content types. [Note: this needs updating in one respect. When you create your pageroutes, you must now specify tabs, not buttons or you won't see the return link from the 'Personal data' section of the user profile back to the main profile area.

Optionally, if you use my Account Types module (http://drupal.org/project/accounttypes), you can assign/associate an account type with a membership type. The README explains the difference between these two concepts and how they can work together.

This module is also aware of OG and my Content Type Administration by Organic Group module (http://drupal.org/project/og_content_type_admin). See the README for how this module interacts with these others.

The README contains the following:

--CONTENTS--
REQUIREMENTS
SETUP/INSTALL
FEATURES
USAGE (Example)
UNINSTALL
CREDITS

See the documentation link below.

This module is complicated to setup and use because of its dependencies. You must read AND UNDERSTAND all documentation for the nodefamily, nodeprofile and pageroute modules before attempting to use this one. Oh, and understanding CCK is a must as well. This precludes use by casual users, whether newbie or not. I'm willing to help, but I won't hold your hand.

Contact me via my Drupal profile if you'd like to hire me to set this module up, modify it for your particular use, or other Drupal/PHP work.

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 ACL module in order to function.

Role control is no longer actively maintained. Please see Auto Assign Role as a replacement.

The session restore module allows sessions (which are stored in a separate table) to be restored upon login.

Example use case: The quiz module stores data related to an ongoing quiz in the user's session. The session restore module keeps track of this session in its own table. If the user logs out or is timed out (for e.g., with the autologout module), the session restore module restores the last saved session the next time he/she logs in. In other words, the user is able to continue the same quiz from the same point the next time he/she logs in.

Google Apps provides a single sign on API (documentation) that enables people to write applications that do user authentication against a local database, and then tell google that the user is authenticated. This modules implements the API in drupal. In other words, once properly setup, this module lets Google Apps instances authenticate against your drupal user database.

The prerequisites for this module are the following: