For authenticated users, presents a disclaimer that must be acknowledged before the user can access site content.
This module is sponsored by ICF International. It was originally created for a U.S. Government agency website, in accordance with security requirements that specify that authenticated users must acknowledge an agency disclaimer.
This module leverages Drupal CAS module to provide Services based solution for CAS Server & Client communication.
This SAML plugin eliminates passwords and allows you to authenticate Drupal users against your existing Active Directory or LDAP server as well increase security using YubiKeys or VeriSign VIP Access via OneLogin. OneLogin is pre-integrated with thousands of apps and handles all of your SSO needs in the cloud and behind the firewall.
Path403 seeks to provide an easily configured mechanism for providing custom access denied messages based on the path that users attempt to access. It can also optionally show a login prompt to anonymous users.
Menu Access Override provides a configuration option to menu items to allow them to be displayed regardless of a user's access rights. This does not override any access control, it only overrides the display of the menu item. Useful for making sure links to members only pages are visible, but present a user with a login screen or other prompt to join.
LAuth is a protocol to authenticate HTTP requests.
There are three actors in LAuth. A CLIENT needs to have access to a USER's resources on a SERVER.
The goal of LAuth is to enable servers to verify the identity of a client acting on behalf of a user without the user having to give to the client the secret he shares with the server.
What does this mean?
For example, let's say Alice have uploaded photos on photos.example.com, using a login name and a password that give her access to the whole range of services offered by photos.example.com.
I'm only starting a module to provide the option to configure privacy settings for fields that have relation with an user.
Access code module allows site visitors to log in using an access code instead of entering username and password. The module aims at expediting the process of setting up and distributing account information to new users. It is intended to be used in cases where user accounts will most likely be accessed a few times only, and you don't want the users to go through the hassle of setting up a username and password.
Description
This module enables the website to permanently store the access tokens
that the module fboauth retrieves from Facebook when the user grants access
to the application that fboauth is managing.
Usage
Once the module is enabled, each user will have a page at /user/UID/fboauth
that allows the user to grant the application all permissions required for all
actions declared in the hook_fboauth_actions implementations.
Smart Contracts is an API with submodules to track when a user has agreed to a contract.
This module differs from similar modules like TOS and UC_termsofservice in that it supports different contracts for different products and scenarios, as well as optionally requiring users to agree to an updated version of a contract before accessing content.
This module is in heavy development at the moment, but is going to production on a couple sites now.
