- Overview
- Getting Started
- Examples
- RESTful API
- auth_info Overview
- Amazon auth_info Response
- AOL auth_info Response
- Blogger auth_info Response
- Disqus auth_info Response
- Facebook auth_info Response
- Flickr auth_info Response
- Foursquare auth_info Response
- Google auth_info Response
- Google+ auth_info Response
- Hyves auth_info Response
- Instagram auth_info Response
- LinkedIn auth_info Response
- LiveJournal auth_info Response
- Microsoft Account auth_info Response
- Mixi auth_info Response
- myOpenID auth_info Response
- Myspace auth_info Response
- Netlog auth_info Response
- OpenID auth_info Response
- orkut auth_info Response
- PayPal auth_info Response
- Renren auth_info Response
- Salesforce auth_info Response
- Sina Weibo auth_info Response
- SoundCloud auth_info Response
- Tumblr auth_info Response
- Twitter auth_info Response
- VeriSign auth_info Response
- VK auth_info Response
- WordPress auth_info Response
- Yahoo! auth_info Response
- Xing auth_info Response
- auth_info Overview
- Reference
- Partner API
- Releases
Engage Flow
Below is a step-by-step diagram that shows how a user will sign in to your website using Janrain Engage, including the appropriate integration points. For another view, see the Mapping Guide (PRO).
Janrain Engage Flow ¶
Steps 1–8, below, refer to the numbered steps in Figure 1, above.
- Click — User clicks the login button (skipped if you embed the Social Sign-In Widget).
- Select — User clicks an identity provider on the Social Sign-In Widget.
- Approve — User clicks approve button at the provider’s site.
- Send Data — Identity Provider sends authentication information to Janrain Engage.
- Send Token URL — Token flows from Engage through the browser to the site’s token_url, or an alternative server page for Client-Side Authentication. (See Authentication for more information on your authentication choices.)
- Fetch Data — Web site securely fetches user data from Janrain Engage using auth_info.
- View Page — Web site shows user its post-authentication web page.
- Save Data — Web site stores user data from auth_info (optional).
- Share — User clicks to share (Facebook, Twitter, and so on) discoveries and activities with their communities with the Social Sharing Widget (optional, see Figure 2).

