Some organization I work with uses Gigya because they are not allowed to store users email address directly into their database.

The alternative approach is to use gigya for auth and then store a salted,hashed representation of the email address in the database. We can hook easily before the creation of the user is made into the database and change the email address but it is currently impossible to hook before the module look for existing user in the db with the non-salted/hashed version of the email.

I've included a simple module_invoke_all that provide a simple hook.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jonathanbardo’s picture

Issue summary: View changes
jonathanbardo’s picture

Issue summary: View changes
FileSize
639 bytes
jonathanbardo’s picture

Status: Active » Needs review
Gigya’s picture

Status: Needs review » Closed (fixed)

A patch provided.