Looking through the code of the plugin it seems the answer is “no.”
So, can it be added? Seems simple enough–Add a filter hook for “user_contactmethods” to include a new “Google Authentication Email Address” field on the user profile. Then, in the plugin check if that field contains data. If it does, use that value when authenticating, if not, fallback to using the standard email address.
You could even include a plugin setting on whether or not you want this field added to the profile page so regular users of the plugin wouldn’t need to be bothered by this addition.
Justin,
I’m really sorry to have missed this post. Please note that support is generally provided via email: contact@wp-glogin.com
I do understand your situation, but I feel it is very unusual and I believe it would not be in the interests of the plugin to develop it so that it is possible for a Google authentication to somehow end up logging in a completely separate WordPress account.
There are security considerations here for a start, and I do think we could risk making things harder to manage – especially if a user finds out about this obscure feature where the site admins aren’t aware of it.
If you are intent and building a workaround, you could consider changing the get_user_by function which is ‘pluggable’ in WordPress. You could override it so that when Google Apps Login calls:
$user = get_user_by(’email’, $google_email);
you return the ‘wrong’ WordPress user when your code sees the google_email you want to map from.
I hope this helps! Thanks again for your suggestion – I really appreciate it and hope you understand why I don’t currently think it is in the interests of other users.
Thanks,
Dan
