User Access & Authentication

An exist module Inline Registration http://drupal.org/project/inline_registration rewritten for Drupal 7

Loginza module integrates Drupal sites with the Loginza.ru service.

Using Loginza, Drupal sites can authenticate new and existing users with popular third-party websites. Currently the following authentication providers are available:

Easy to use Facebook login using Open Graph API.
- no Javascript
- no external libraries
- easy configurable, only set up App ID and App Secret
- easy to use for user - one click for login, one click for access permissions on Facebook
- no other features, only easy registering and login for your website by Facebook

Provides two context module conditions related to a user profile page being viewed:
1) Evaluates the role(s) of the owner of the user page being viewed.
ie. Return true if the user page being viewed is owner by user with XXX role.

2) Evaluates whether the global user (logged in user $user) is viewing their owner user page(s)

Audience provides an abstract definition of user groups and types in a given context. These definitions are called "Audience presets" and can be used by other modules to control different types of audience related actions or permissions. By using CTools these audience presets are exportables and can either get stored in a database or live in code provided by modules.

This module changes the entire profile

of a Drupal site user. The updated profile page not only the users history, but also his entire social status.

This project integrates the New Zealand Government's iGovt service (https://www.i.govt.nz/) with Drupal (currently version 6). It is based on SAML2 authentication and relies on the SimpleSAMLphp service provider to talk to iGovt and Drupal.

This module is currently in development with very little instruction or direction as yet. But that will change.

This module enable users to login with 3th party services.

The following services are supported:

• Facebook
• Twitter
• Hyves

Provides a copy of the standard Permissions form for users that don't have the permission "administer permissions", but do have the permission "access subpermission form". The form looks identical to the standard Permissions form, but with only a subset of the standard Permissions. Permissions marked as "restricted" are always removed from the form.

An administrator (with the permission "administer subpermissions") must specify which permissions should be displayed on the subpermission form.

Provides each user with a unique user key, which can be used around the site, as well as reset on demand.