Janrain Backplane: Livefyre Support
-
Please address first
https://www.ads-software.com/support/topic/janrain-capture-ui-inconsistent-backplane-namesProblem
Janrain Registration works as should in logging a user through backplane in support of both janrain and livefyre. That is, janrain showslog out
in place of all shortcode declarations as well as livefyre listing the logged in user for comments. However, when a user logs out, backplane is not working in signing out a user from both services.Discussion
If a user logs out of Janrain, through its shortcode, we are able to successfully log out of Janrain services and the WordPress session. Upon refresh, the shortcode declaration now requires we sign-in. A quick check of related federate sites shows the event was emitted and user is now signed out of all sites. Nevertheless, if we look at an article that has livefyre enabled, we see that a user is still logged in.The same situation applies if we use livefyre to sign out. When you select sign out from livefyre, the current session of livefyre has ended and a user is logged out of all related federate sites. However, even after manually refreshing the page, the shortcode shows the link to log out. In both cases, you can sign out of one but not the other.
Our implementation of livefyre registration is strictly based on the recommended workflow from:
https://answers.livefyre.com/developers/identity-integration/janrain-capture/
More specifically, following the same object creation for the authentication delegate.
A few initial ideas that we’ve played around with include forcing a redirect to the same page, with a logout query, after the auth delegate runs the logout function. We would follow a similar action that you have injected in your shortcode declaration when a user is signed in:
https://php.hgv.dev/wp-login.php?action=logout&redirect_to=http%3A%2F%2Fphp.hgv.dev%2Fpreparation%2Fhack-cash-449%2F&_wpnonce=ca9e59831e
This code is generated from your
janrain-capture-ui.php
:
$href = wp_logout_url( self::current_page_url() );
This does work in logging a user out from both janrain and livefyre. However, when a user attempts to log out from the generated shortcode link, that is from janrain, a user is signed out of janrain but as mentioned above, is not logged out of livefyre.
So while we can resolve this issue one way, the problem shouldn’t exist at all if backplane is correctly working with both services. We understand that in a successful flow, we would be responsible for any asynchronous UI changes that need to occur to properly reflect livefyre sign out. We also understand that wordpress session also comes into play in logging a user out.
Thanks for reading!
- The topic ‘Janrain Backplane: Livefyre Support’ is closed to new replies.