Drupal 7.39 will break this module before 1.6. ALL sites using this module should update to 1.6 this module
Provides formAPI elements for selecting & validating single or 'segments' of users according to
Presents a dropdown or autocomplete field which accepts uid, email and/or username.
Offers front-end configuration of
By default Drupal is very secure (especially Drupal 7). However, there is a way to exploit the system by using a technique called username enumeration. Both Drupal 6 and 7 have this issue, but it is much worse for people using Drupal 6. This is because Drupal 6 does not have any built in brute force prevention. When an attacker knows a username they can start a brute force attack to gain access with that user. To help prevent this, it is best if usernames on the system are not easy to find out.
This module allows nodes that are created by an anonymous user to be handled by the authenticated user who logged in from a same machine. The connection is identified and built automatically.
When an anonymous user who has created some nodes logs in, the module will identify the anonymous user with the authenticated user, and automatically created duplicated nodes for the latter. Every change on those nodes made by either the anonymous or authenticated user will be applied to the corresponding nodes.
While Drupal provides capabilities for commentng for both anonymous and authenicated users, it provides no easy way for authenticated users to post comments anonymously without having to manually log out first. This is not only inconvenient to users; it also poses a problem on sites that may choose to implement a "paywall" or other means of limiting access to content but wish to allow for anonymous commenting.
This module provides a simple single sign on solution based on OpenID and native in Drupal. It is single the provider (server) module, related to: OpenID Single Sign On Relying Party
You can set up a central provider (which ideally is another instance of Drupal) and a lot of another (Drupal) websites (so called relying parties). This way the users can login to every single relying party website using a centralized login provider where authentication is happening.
This module provides a simple single sign on solution based on OpenID and native in Drupal. It is the relying party counterpart for a server based on OpenID, related to: OpenID Single Sign On Provider
You can set up a central provider (which ideally is another instance of Drupal) and a lot of another (Drupal) websites (so called relying parties). This way the users can login to every single relying party website using a centralized login provider where authentification is happening.
A sandbox project for extra authentication modules for the Services Module
This module allows users, of a specific role, to block site users (individual or all) for a defined time period. Users can be banned by admin for a definite time period. Users can be ban or temporarily block by individually or collectively by users roles. Means there is a sub module present here from where admin can ban users by role wise. This way we can make disable user log in for definite time period.
Temporary blocking of users or ban user will be automatically lifted after the defined temporary blocking date or temporary blocking time.
Warning: Under construction!
This module will allow roles to be grouped into sets and dynamically assigned to users per page load.
This module operates by generalizing the concept behind Organic Groups User Roles, and is intended to provide all the advantages of dynamic role assignment and separation between access control logic and friendly access administration.
Sandbox for new additions to the Request Invitation module.
