User Management

Module is needed for changing authentication settings for restricted area on site. Module defines SSL users and sets single password for all of them in .htpasswd.

This module was created for Janssen Contracting Co., Inc..

Instructions

You should manually create .htacces and .htpasswd files. Changes in SSL users settings tab will affect on .htpasswd file.

If restricted area is located in /home/www/area/, so there should be /home/www/area/.htaccess file with following lines:

Misery is a module designed to make life difficult for certain users.

This module allows administrators to hide a users posts from all other users. This is an effective strategy for dealing with troublesome users as it discourages attempts to evade bans.

This module unobtrusively adds additional checkboxes to the permissions form located at admin/user/permissions - the additional checkboxes provide a much friendlier interface for dealing with the hundreds of checkboxes that accumulate on the permissions page as roles and modules are added to a Drupal installation.

On a test Drupal site I set up with 6 user roles, 105 core and add-on modules enabled, 9 content types, and the content permissions module enabled, there were 138 distinct permissions and 828 individual checkboxes on the permissions page. To initially set up the permissions to something sane, it took me about 17 minutes. On my first attempt of using this module after fully developing it, after wiping and restoring the database from a back up, it took me around 5 minutes to set up the same permissions. The point is that this module will save you time, especially on large sites.

Concept

This module is for sites that allow users to create an account, but require administrator approval for account activation. This module creates a block that shows a list of unactivated user accounts, with links to their account pages. This block is visible for anyone with 'administer users' permission, and will not be shown to any other users.

Overview:

This module allows users to mark administrator selected CCK fields as Public (visible to everyone), Hidden (visible to node author, hidden from everyone else) or Private (visible to node author and "friends"; see requirements section below).

Description:

• The field settings screen provides a new option to enable privacy options for fields. This option is global and affects all content types where the given field is shared. The default privacy status can be specified.
• This module supports all kind of fields, and even fields in multigroups.
• In the node edit form, a new option to configure field privacy settings will be available as a small icon next to the fields where this feature has been enabled. This is only available to users with "edit privacy options for field %field_name" permission.
• Users with "view private data for field %field_name" permission are excluded from privacy restrictions. This feature combined with node revisions allows community managers and/or site moderators to monitor changes to privacy settings.
• Builtin support for node revisions and Diff module.

Requirements:

• Content Construction Kit (CCK): CCK version 2.5 or higher is required (ref.).
• To enable the "Private" status for fields, you need one of the following modules: Flag Friend, Friendlist API, User Relationships. CCK Private Fields module includes ready to install mini-modules that provide builtin support for any of these friendship related modules.
• The privacy options dialog requires jQuery UI (either version 1.6.x or 1.7.x).

Overview

Gigya's Customer Identity Management platform helps companies build better customer relationships by turning unknown visitors into known, loyal and engaged customers.

With Gigya’s technology, businesses increase registrations and identify customers across devices, consolidate data into rich customer profiles, and provide better service, products and experiences by integrating data into marketing and service applications.

The sole purpose of the Alter Profile Page module is to bring more of social networking, MySpace-ish look to Drupal's user profile page.

Enabling the module will change what appears on the users' profile page(s). By default, the Drupal core sets the profile page to display a section called History, under which you'll see Member for which then displays XX weeks YY days. Please see the attached screenshot for a before and after look at what the module does.

Permit own permissions provides a new permission, share permissions, and anyone given this permission can add or remove any permission she has from any role. They will be able to access admin/people/permissions

Problem:

A site is beautifully set up and guards against catastrophic user error (blowing things up) while giving the person you made it for as much flexibility and power to add to it as is possible... almost.

This module enables you, with very easy UI, to set or unset cookies for users when they login or logout from your site.

use cases:
* Some CDN allow bypassing CDN cache when a special cookie with specific value is set for a site visitor.
* *add more use cases*