Janrain Product Releases

Documentation 2013.20

Tue, 14 May 2013 20:37:42 +0000

Expanded the Engagement Extensions section with our current partners using the Backplane protocol.
Updated documentation to reflect that LinkedIn requires r_network permission in order to use get_contacts.
The default User Registration solution email templates have been updated.
Removed the verifiedEmail value retured from the Foursquare auth_info response.

This was removed due to a security hole.
Improved parameter definitions for register_native_traditional.

Explain that the email parameter has a variable field name, and the parameter may actually have another name if defined differently in the flow.
Added backplaneChannelExpires JavaScript setting to the User Registration Widget.

This is an optional setting for defining the expiration of channel cookies.
Added the Custom Scoping Guide.

This is a new feature allowing sites using the same widget to request a different set of permissions. It is set with a JavaScript setting.
Added new backplane2_extra_attrs JavaScript setting that allows customers to define additional attributes which are returned in the capture field of a backplane payload.
Custom error messages added to the User Registration Widget. These are added using the Event system, specifically the linkError, and customError events.

Tue, 14 May 2013 19:43:18 +0000

Tue, 14 May 2013 18:34:25 +0000

Now works with all versions ofCapture.
Added social sharing capability.
Added plural support for account mapping.
Added support for Backplane 2.0.
Updated default screens.
Changed cURL to drupal_http_request.
Fixed an issue relating to the OAuth URL endpoint.
Fixed issue with logout link ceasing to work when new Capture SSO is enabled.
Fixed issue with SSO logout from site with iframe busters.
Fixed issue with Access Denied result when clicking email verification with logged in user.
Fixed handling of PHP ‘undefined index’ warnings for fresh installs.
Fixed issue with fresh installs resulting in a PHP exception.
Fixed JavaScript console warning and user/edit page not found issues in Capture.
Fixed broken Drupal-generated login/register links.
Fixed IE8 HTML parsing error when viewing user profile.
Fixed IE8 issue where janrainCaptureWidgetOnLoad() did not always get called.
Fixed so that users’ email addresses are never stored in Drupal.
Fixed #1900692: Provide SSO URL as Token.
Fixed IP:Port issues.
Fixed Verify Email and Forgot Password screens.
Fixed miscellaneous Internet Explorer issues.
Fixed miscellaneous SSO issues.

Tue, 14 May 2013 17:09:20 +0000

Mon, 13 May 2013 21:35:49 +0000

Added functionality for rotating a client secret, while still allowing the old one to work for a short amount of time.
Several performance improvements.
Fixed an issue causing Capture to occasionally yield unexpected errors.
The register_native now requires the parameter form.
Now support log in using a different entity type for each client (e.g. for each site).
Log in events using the native endpoints will now be published to Backplane.

Tue, 07 May 2013 16:14:13 +0000

Fixed a bug where “keep me logged in” checkboxes change state after a user attempts sign in with invalid credentials.
Fixed a bug keeping users from performing social registration within a mobile web view.
The response_type parameter is now no longer required for calls to the ‘native’ Capture endpoints.
Error responses from the ‘native’ Capture endpoints now contain an “error_description” property to be consistent with the other Capture APIs.

Mon, 06 May 2013 17:10:12 +0000

Thu, 02 May 2013 18:02:35 +0000

Fixed: Windows Live providerSpecifier returns null (breaks XML flavor of auth_info).
Restored force_reauth capability for Facebook.
Fixed: Server error 500 returned for get_user_profile in Share Widget.
Fixed: get_user_data returning 500 when identifier isn’t found.

Thu, 02 May 2013 17:09:23 +0000

Wed, 01 May 2013 22:23:32 +0000

Fixed a bug where verification emails were not being sent upon user registration in the native API.
Required fields missing from POSTs to the native API are now validated properly.
The native API now requires that the supplied client id have the login_client feature.
Added support for validation rules in the flow to be configured via a setting (configurable in the dashboard). Currently only the minYears flow validation type has this support.