Integrations

Looking for Drupal 8 support?

See the Drupal Connector for Janrain Identity Cloud from CI&T at https://www.drupal.org/project/janrain_connect.

Using Janrain Social Login, Drupal sites can authenticate new and existing users with popular social networks, map user profile data from these websites to Drupal fields, and share Drupal content with a user's friends on their social networks.

The module helps Drupal websites quickly and seamlessly integrate with 30+ social networks including Facebook, Twitter, Google, Yahoo!, LinkedIn, AOL, PayPal, and Microsoft Account.

Instead of having to integrate with each of these sites on your own (and manage API changes over time), Janrain Social Login does the heavy lifting for you. Using this module, you can get setup in under 10 minutes. The result is an accelerated user registration process, an enhanced ability to gather user data, and increased site traffic from the viral promotion of your content.

Module features

Block, Allow or Reroute E-mails based on the mail ID. Each mail ID rule can reroute to a primary or specific E-mail address.

Follow adds sitewide and per user links that link to various social networking sites. The links reside in two blocks. The Follow Site block lists all the links for the site itself, and by default is visible on all pages. The Follow User block lists all the follow links for the user and is visible only on user profile pages.

Ubercart has included the Recurring Fees module as a core module for some time now, allowing users to associate recurring fees with products that customers must pay for via credit card. Unfortunately, the module was never really there in terms of practical uses and extensibility. Due to its limitations and to its relatively minor importance to the Ubercart project as a whole, the development team decided to move it into contrib space where it could mature without limiting or being limited by the core Ubercart development cycle.

UC Recurring Fees 6.x-1.0 is a straight migration of the code from Ubercart as it stood at its latest point in the 2.x development cycle. It was removed between RC1 and RC2, as we forgot to nail down the issue prior to tagging the 6.x-2.0-rc1 release. Several community members have been developing code and ideas to greatly improve and maintain this module, and they will work on it through this contrib in the 6.x-2.x version and beyond.

This module provides a bridge between Drupal and EZProxy.

EZProxy helps provide users with remote access to Web-based licensed content offered by libraries. It is middleware that authenticates library users against local authentication systems and provides remote access to licensed content based on the user’s authorization.

There are three main methods of authenticating between Drupal and EZProxy:

• External Script Authentication
• CGI Authentication
• Ticket Authentication

This module provides three methods. Here are the use cases:

1. External script authentication
When you click on a link to go to an EZproxy database, EZproxy will ask you to login. The username and password entered will be sent to Drupal and Drupal will check if the user exists in the system and has the 'access ezproxy content' permission. If the user does have permission, Drupal will report back to EZproxy with a successful logon attempt.

2. CGI authentication

This project will be work on a new Analytics module to possibly replace Drupal core's Statistics module.