- Getting Started
- RESTful API
- auth_info Overview
- 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
- LinkedIn auth_info Response
- LiveJournal 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
- Windows Live auth_info Response
- WordPress auth_info Response
- Yahoo! auth_info Response
- auth_info Overview
- Partner API
A data record associated with one or more of a user’s identity.
When referred to in the context of an Engage application this is a public string which uniquely identifies the application.
Protocol used for sending messages to Backplane enabled widgets through a Backplane server. Useful for sharing user identity and other information to multiple vendor widgets on a site.
Can refer to either the API call used to fetch a user profile from Janrain, or to the data structure containing the user’s profile data that is returned by that call.
Browser software used by users to access the sites on the internet, such as, Mozilla FireFox, Google Chrome, Apple Safari, or Microsoft Internet Explorer.
Short for “canonical name”, a type of DNS record that points to a second DNS record. For example, signin.yoursite.com frequently uses CNAME to point to your Engage realm, which in this case might be yoursite.rpxnow.com.
A website operator that uses Janrain products and services.
A custom domain is a domain chosen by the customer to display during the sign-in process. If you, the customer, choose not to use a custom domain, the rpxnow.com domain appears instead.
The web-based user interface for Janrain applications. The user manages their account and creates widgets from the Dashboard.
When referring to the Engage dashboard, a list of domains which may host your applications’ token URL (or other server page if you are using Client-Side Authentication).
Short for Fully Qualified Domain Name, for example, www.janrain.com.
A provider’s unique id for a user. Represented as a URL except for some older Engage applications.
A package of data about a user and their profile.
The user data obtained from the Identity provider for authentication.
An Identity Provider, such as Facebook, Google, Hotmail, or Yahoo!
The process of incorporating Janrain products into your website.
A standard protocol that provides users (and developers) a secure way to access their address books and friends lists without having to take their credentials or scrape their data. Portable Contacts is sometimes abbreviated as POCO. For details see: http://portablecontacts.net/
Data associated with a user. Sometimes includes demographic information.
This refers to having different levels of access to profile information on different parts of a website. For example, you may want your website to have access to additional information, such as a Friends list, when an end user establishes a Social Sharing link.
See Identity Provider.
Generally the first part of a FQDN, like the www in www.janrain.com.
A Relying Party (sometimes RP) is the Janrain Customer’s website that relies on one or more identity provider is known as an RP (Relying Party).
Legacy name of Janrain Engage, and part of the website rpxnow.com where you create Engage and Capture applications.
The customer’s computer hardware and software that offers web pages and web applications to users.
The process of authenticating a user on a website.
A customer’s website that consumes identity information, also an RP (Relying Party).
SSO (Single Sign On)
A feature that allows a user to sign-in once and be authenticated across sites and domains. SSO is core to Janrain Federate (formerly called OPX).
A piece of data that acts as a key to access additional information.
The path to the file on the customer’s site that receives the access token from Janrain.
for example, http://www.example.com/rpx.php
See Authentication for more options.
As Capture uses the terms, unique means globally unique across all records, while locally-unique means that the name must be unique only within the same parent record, but two different user records can have the same value.
A visitor at a customer’s site, also called End User.
The list of authorized sites configured in the Dashboard.
A ready made element configured in the Dashboard, and designed to be dropped into your existing code.