Issues implementing Janrain for Open Authentication

Options
Hello Community,


I was wondering if anyone has had trouble smoothly integrating Janrain open Authentication with Luminate Online and Luminate CMS. Despite following the documenation provided I haven't been able to get everything working.


So far I have managed to get open authetication working on Luminate Online pages such as our main login page. The only issue I face on the luminate online side is that anytime I perform a test and login with an account (my linkedin) I get an email saying the account has been linked, every time even though I have already linked the account. Is there a way to set how many times you get the email that tells the user the account has been linked?


Now for the major issue, I cannot seem to get Janrain Open Authentication to work on CMS pages. I have included the login module in our page wrappers (using the embed module functionality>>luminate online content>>external login>>open authetication login) which displays the various social media login options and when I click on them they do display the proper login popups for users to enter in their social media login info, however when you attempt to submit that information, you are redirected to a "We are experiencing technical difficulties page." No other error displays, it does direct the the proper logged in page like when you log in through a luminate online page. Has anyone else had this issue and have a suggestion to get the login to work properly for CMS pages?


Thanks so much!
Tagged:

Comments

  • Hey there Jordan! We reached out to support and opened up a case on your behalf so you can have answers soon. 


     
  • Hi Jordan,


    Not sure if you were able to find a work around for this, but there is a solution available.  You'll need to adjust the POST method being used by Janrain.  Instructions are below:




    2. Click on the Manage Engage App icon (the blue word bubble) next to your Engage App Name 


    2. Click Settings


    3. Scroll down to the Migrations panel and uncheck,"POST tokens to token_url"


    4. Click Save


     

    I hope this helps!
  • Awesome, thanks so much Jes. This did fix the log in issue, we can now log in through CMS.


    We still need to sort out the emails being sent everytime someone connects an account and the links to the users social media profiles also don't work in constituent 360 but this is a big step forward!
  • You're welcome Jordan!  As far as the issue with multiple "account linked" autoresponders, this is slated to be fixed with the 16.6 release.


    Glad this helped!

Categories