- Social Sign-in Widget
- Implementation Guide
- User’s Guide
- Social Sign-in Widget API
- User Registration Widget
- Widget Basics
- Implementation Guide
- User Guide
- Default Email Templates
- Default UI Flow
- Mobile Support
- Using jQuery
- Saving Traditional Sign-in User Data
- User Registration Widget JS API
- Technical Overview
- Social Sharing Widget
- Provider Setup Guide
- One-Click Sharing Widget
- Legacy Sign-in Widget
- Legacy Sharing Widget
Legacy Server Integration
This widget has been deprecated.
When creating new sign-in widgets, use the Social Sign-in Widget.
Janrain’s new Social Sign-in Widget was released in September of 2011 and provides many new features and performance improvements. To learn about the new Sign-in Widget, visit the Social Sign-in Widget page.
It is Janrain’s policy to maintain and support legacy UI widgets for 12 months following the release of new replacement widgets. When the 12 month support period expires, Janrain will no longer add features or provide maintenance updates for the legacy widget, such as support for new versions of web browsers. Support for the legacy Social Sign-in Widget will end on October 1st, 2012.
Q: Does this mean that my old Sign-in Widget will stop working on October 1st, 2012?
A: No. Your widget will continue to work, and support all the browser versions that were previously supported, however it may not work with the latest browser version.
Q: Is it hard to switch to the New Sign-in Widget?
A: No, it is very straight forward and we have instructions for you to get started on the Social Sign-in Migration Guide page.
This page describes how to integrate the Legacy Sign-In Widget with your server.
Code Examples ¶
You can find code examples in many languages for handling the posted token URL in our repository at Git Hub. There are samples for PHP, Ruby, Java, C#, Perl and more.
For security we communicate authentication information to a receiver placed on your server known as the Token URL. The Token URL is a simple web page that contains a few lines of code that receives the authentication information from Janrain, optionally fetching and storing user profile data.
It is typically placed in the sites root directory and named something like rpx.php, for example:
When configuring the sign-in interface, you supply a token_url parameter. This is where the user will POST their token after completing the authentication process. You must extract the token and pass it into the auth_info RESTful API call.
|token||String||The token used for the auth_info API call.|
If the user cancels the sign-in transaction, the identity provider may make a POST to your token_url without the token parameter.
Passing Data ¶
You can pass additional parameters into the token_url. This enabls you to pass data to the post login page.