Incomplete integration with Janrain (RPX) login module. Loginza is another one. [#1122210]

I'm currently using: http://drupal.org/project/rpx ...and there's also: http://drupal.org/project/loginza

For rpx, clicking on the twitter icon gets me the jainrain overlay, which takes over the fancy login overlay page. It doesn't provide the right link though and it gets me this error message: "The token URL or xdReceiver has not been whitelisted"

So there's a source link problem for integrating between the two.

Social login providers obviously increase registration rates. Also, I couldn't find the login block for this module for D7 on the blocks page.

I'm also using captcha (not recaptcha), and the securelogin module.

Nice module by the way.

Comments

Comment #1

threading_signals commented 9 April 2011 at 23:42

Solved the token URL or xdReceiver portion by logging in to janrain and adding the "www" subdomain.

The fancy login overlay portion can't regain focus if the user wants to cancel janrain login.

Comment #2

jaypan

Victoria, BC

commented 11 April 2011 at 02:33

Status:

Active

» Postponed (maintainer needs more info)

I'm sorry, I don't know what rpx and jainrain are. Can you give me some more information about what you are trying to do, and what modules are conflicting? Thank you.

Comment #3

threading_signals commented 11 April 2011 at 16:20

Jainrain changed their name from rpx - the module provides additional login providers such as for facebook, twitter, etc. Your module gives an overlay for logins, whenever there is a link to example.com/user/login. Jainrain and loginza adds extra login provider links to the login box, and I posted the links for those two independent modules above - I'm actually only using Jainrain. When you click on those provider links provided by Jainrain, there's another overlay over your overlay. It doesn't send information back to your module if the user decided to cancel their login to facebook, twitter, etc. - only your overlay remains as it should be - however, only the processing swirling circle icon remains - no form fields are visible. That's the part I'm referring to as the problem. It doesn't give control back to your module. It is better if the source module fixes it, instead of getting all the additional login providers to fix it (because extra login provider modules should only go back to the current page), but it depends on the architecture and any standards in place.