Mobile SDK Integrations
Authentication via SDK-managed UIWebviews and the Mobile System Browser
This is the default and recommended method to integrate a native mobile app. In this integration, the Janrain mobile libraries control the Social Login integration and spawn the necessary UIWebview or native browser to interact with the Social Login application. If you are implementing Registration, the mobile libraries also manage communication with the oAuth API endpoints to facilitate the whole process.
|Social Login-only Integration Guide - iOS||For setting up Social Login without Registration on iOS.|
|Social Login-only Integration Guide - Android||For setting up Social Login without Registration on Android.|
|User Registration Guide - iOS||Important overview of the types of Registration supported by the iOS mobile Libraries.|
|User Registration Guide - Android||Important overview of the types of Registration supported by the Android mobile libraries.|
|Registration Integration Guide - iOS||Setting up Registration with the iOS mobile libraries.|
|Registration Integration Guide - Android||Setting up Registration with the Android mobile libraries.|
|Xcode Project Setup||Important tips on getting started with XCode. This is a must-read for iOS developers!|
|Android Studio Project Setup||How to import the Android libraries into Android Studio.|
|iOS Upgrade Guide||Every developer should refer to this document when upgrading from a previous version of the mobile libraries. Includes breaking changes and important upgrade information.|
|Android Upgrade Guide||Every developer should refer to this document when upgrading from a previous version of the mobile libraries. Includes breaking changes and important upgrade information.|
This integration potentially provides the best end-user experience for Google, Facebook, and Twitter users.
In this integration, if the user has already set up accounts on the user’s device for these providers, the mobile libraries can be configured to interact with the provider’s native mobile libraries to allow login without the end user having to re-enter a password. Note: This functionality is not supported for any other providers.
This integration requires additional developer effort because the developer is responsible for getting the necessary oAuth token from the native provider’s mobile libraries.
Note: Follow the Mobile SDK Integration using Social Login Authentication instructions before attempting to implement Native Authentication.
|Native Authentication Guide - iOS||Advice on working with the iOS Native Provider’s libraries and the Janrain mobile libraries.|
|Native Authentication Guide - Android||Advice on working with the Android Native Provider’s libraries and the Janrain mobile libraries.|
This integration uses the Registration and Social Login widgets that are used in a typical website integration.
The developer calls the Widget that is hosted on the developer’s web server through a UiWebview (or equivalent). In most cases, the widget is configured to post the results to a server that the developer controls (which can serve the results back to the mobile application).
|Implementing Social Login||The best starting point for getting started with Social Login and configuring the Social Login application settings.|
|Implementing Registration||The best starting point for getting started with Registration and configuring the Registration application settings.|
|Social Login Authentication Token URL iOS/Android||A brief example on how to work with the Social Login token URL and redirection.|
Native API Integration using the Janrain REST API
For this path, you write your own integration and workflow around the Janrain REST API endpoints. This integration does not use the Janrain mobile libraries. Instead, you will largely write your own libraries to interact with the REST API as needed.
Getting Support for Mobile Integrations
When filing a mobile support ticket through Janrain’s support portal, you will get the quickest response by including the following information in the support ticket:
The complete log files from your development environment (Xcode or Android Studio). These log files should include all the log data from the start of the application until the end user has acknowledged any error dialogs. These logs often contain useful configuration data from library startup and initialization that points to why a particular error is occurring.
The model and OS version of any physical devices or simulators that are being tested against.