The Mode module is a utility module that allows administrators to manage different permission sets and switch between them conveniently. It works by manipulating the permissions table during each switch.
Example scenarios where this module will prove useful:
This very light-weight module allows additional permissions to be created and managed through a administration form. It uses the menu access system to allow or dissalow access to it.
On the administration page a user is able to create a permission with name and path(s).
These permissions can then be assigned to roles on the permissions page.
This module allows control (editing) access to sub-trees in a book.
This module is loosely based on Book Access but instead of delimiting access to a book (as Book Access does), it allows you to set fine-grained permissions for each page in the book and all its children.
It is ideal for big organizations with lots of ramifications and lots of information to present.
28-Jan-2012: I no longer have time to work on this module and no longer use it in any projects I'm involved with. Please contact me if you're interested in maintaining it.
Comment Login adds a user login section to the standard node comment form. This allows users to log in at the same time that they post a comment, and remain logged in thereafter. This module has the effect of disallowing anonymous commenting, but still showing the form to anonymous users with the requirement that they also supply a valid account to post.
Easylogin allows the admin to give a permission to users so they are able to log in via an url. Yes, I know what you're thinking, but wait! This could be useful for demoing, and allowing a simple login whilst devloping and prototyping alongside a client, etc.
Install, and it will create a random login URL for each active user.
By adding an optional ?destination=node/324 will redirect the user to the node/324 url after login. The default destination is <front>. The module will also adhere to the destination set with login_redirect.
Subscribe users to organic groups.
Existing user can be subscribed to an Organic Group by filling in an autocomplete field with their username.
In development: New and existing users can be mass subscribed to an Organic Group by importing data from a CSV file.
By default, Drupal allows only users with the Administer menus and menu items permission to add, modify or delete menu items.
Menu Admin per Menu allows to give roles per menu admin permissions without giving them full admin permission.
For instance, you may let certain users manage the items of the Main or Navigation menus but not those of the Management menu.
SlAuth is a module to allow authentication using SecondLife / OpenSim credentials ( login / pass ).
The user needs first to register to the Drupal site using the normal way and should use the login name with firstname and lastname separated by a space.
The admin panel allows you to change the login Uri and to define the login flow.
Web applications that need to access services protected by a user's Google or Google Apps (hosted) account can do so using the Google Authentication service. This service lets web applications get access without ever handling their users' account login information. Many but not all Google services support the Authentication service; check first with the service you want to access.
Google offers two libraries for handling authentication: one using the OAuth open standard, and a second interface called AuthSub, developed prior to the release of the OAuth standard. This module implements the AuthSub interface.
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.
