First experiences with React Native: bridging an iOS native module for app authentication

Wed 09 May 2018 By Skip

Category: React Native Tagged: Mobile Android API Security React Native

First experiences with React Native: bridging an Android native module for app authentication

React Native bridging Photo by Liu Zai Hou on Unsplash

My company, CriticalBlue, provides a remote mobile app authentication service called Approov. An Approov SDK is provided as a drop-in library to native iOS and Android app developers.

With many of our customers using or experimenting with React Native, I wanted to provide a convenient Javascript module which exposes the native Approov SDK functionality to React Native developers.

Overall, creating my first React Native native module was surprisingly straightforward. All code for my initial proof of concept is available in a github repository.

This story describes bridging to iOS native modules. For the same example targeting Android, see First experiences with React Native: bridging an Android native module for app authentication.

React Native Bridge

For react Native, Facebook provides a solid getting started guide which goes over the basics, including how to set up an application and how the underlying UI components differ from the usual React web elements.

React Native bridge from React Made Native Easy

Architecturally, there are two important threads running in each React Native application — one a main UI thread and the other running a Javascript VM. The two threads interact through a bridge whose communication is asynchronous, serialized, and batched, decoupling the two systems as much as possible.

While the bulk of the React Native app is described in React and runs on the Javascript VM, the UI is rendered using the native platform’s UI elements, and actions which alter the app’s UI are passed as messages through the bridge from the VM to the app’s main UI thread.

System functionality and libraries developed for the native device environment can be exposed to the Javascript VM using React Native’s native module interface and accessed through the React Native bridge.

Approov Native SDK

The Approov SDK is a drop-in native iOS or Android library. It interfaces with the cloud-based Approov authentication service which validates that the app is genuine, untampered, and not a bot. An app integrity token is returned from the authentication service, and that token is sent with each API call to ensure that the back-end API service is dealing with a known and genuine front-end request.

The basic operation we will expose in our native module proof of concept is fetchApproovToken(), an asynchronous operation in the native SDK.

Approov API Protection Approov-protected API call

Before each back-end API call requiring app authentication, the client app makes a fetch token request. If a fresh token is needed, the SDK makes a remote attestation request, and the attestation service cryptographically authenticates the app and responds with an app integrity token.

The token has a short lifetime and is signed by a secret known only to the Approov service and the app’s back-end service. No secret is stored in the app, and in fact the app does not know whether the returned token is valid or not. The app simply adds the integrity token to the back-end API call, and the back-end server validates that the token has not expired and is properly signed before processing the request.

Approov Demo Service

Approov offers a downloadable demo which provides demonstration iOS and Android SDKs and a back-end service with two endpoints:

We’ll use the iOS SDK with the back-end service to demonstrate a simple React Native app using Approov. For the Android version of this example, see First experiences with React Native: bridging an Android native module for app authentication.

Saying Hello

I started my React Native project using create-react-native-app (CRNA). Follow the CRNA installation instructions to setup your React Native environment and then:

$ create-react-native-app rndemo

I will be adding native code to the app, so go ahead and eject now from create-react-native-app:

$ cd rndemo
$ yarn eject
...

Ejecting is permanent! Please be careful with your selection.

? How would you like to eject from create-react-native-app? React Native: I’d like a regular React Native project.
We have a couple of questions to ask you about how you’d like to name your app:
? What should your app appear as on a user’s home screen? RN Demo
? What should your Android Studio and Xcode projects be called? rndemo

Wrote to app.json, please update it manually in the future.
Generating the iOS folder.
Generating the Android folder.
...

Select a regular React Native project and name it as you wish. The iOS and Android projects are generated, and you will need Xcode and/or Android Studio build environments installed. Native code will be added to the native Android project later on.

We will experiment with a very simple proof of concept app that will use the demo server hello endpoint to validate our network connectivity.

React Native implements the fetch API for networking. We combine the connection check, UI rendering, and styling all in theApp.js file:

The top-level App component is registered in the index.js file.

The main view is rendered by a stateless view component which displays a choice of image and a status message:

I am using iOS for these examples, but this works similarly on Android. Fire up an iOS simulator (you may need to launch Xcode for this). In the rndemo directory, launch the app:

$ cd rndemo
$ yarn run ios

You should see a screen like this:

Splash Screen

Push the Test Hello button and you should see a connected message if everything went okay:

Say Hello

This validates network communication between our React Native app and the demo server.

To run on an actual iPhone, connect the iPhone to your Mac. In Xcode, open the React Native iOS project, select the iPhone as your target and run the application.

To test for no connection, if running on the simulator, disable your Mac’s WiFi or networking and push the Test Hello button. If running on a phone, set airplane mode and then push the Test Hello button.

The Approov Native Module

The Approov demo package includes a README, the iOS and Android Approov demo libraries, sample clients, and app registration tools. Download the demo package, and save the app registration token which is included in your download email.

The Approov SDK includes the native code we want to expose to React Native. It must be included in the iOS or Android native projects which were generated when we ejected the create-react-native-app. For iOS, this project is located at rndemo/ios. Add the Approov SDK framework into the iOS project by following these instructions from the Approov docs.

The iOS Approov SDK currently does not support bitcode, so you should set Build Settings -> Build Options -> Enable Bitcode to No in your Xcode project settings.

In iOS, a native module is an Objective-C class that implements the RCTBridgeModule protocol. Our example will mix Objective-C and Swift to register and implement the bridge to native code.

We’ll start by creating the Approov bridge class in Swift with a fetchApproovToken() call which wraps the asynchronous native fetchApproovToken() call and settles a promise when the token fetch completes.

In the fetchApproovToken() call, the promise is settled by calling the resolve RCTPromiseResolveBlock or the reject RCTPromiseRejectBlock. Our implementation simply resolves with the fetched token if successful or a NO_TOKEN sentinel on failure. Both closure blocks are marked with @escaping attributes to indicate that they may complete after the fetchApproovToken() call completes. @objc modifiers are used to export the class and functions to the Objective-C runtime.

The Objective-C implementation connects the Objective-C exposed Swift class to the React Native bridge. The RCT_EXTERN_MODULE() macro registers the Approov class, and the RCT_EXTERN_METHOD() macro exposes the fetchApproovToken() call.

Whenever you mix Swift and Objective-C in the same project, you need a bridging header to expose the Objective-C files to Swift. It must include the React Native bridge headers.

On the Javascript side, the Approov native module will now be included in the NativeModules imported from react-native. In our implementation, Approov.fetchApproovToken() returns a normal javascript promise:

Bridging the native and Javascript environments was a bit confusing when mixing Swift and Objective-C, but in the end it required only a small amount of code.

Interceptors

Many networking libraries, such as Axios and OkHttp, include the concept of an interceptor. Interceptors can be used to intercept network requests and responses and inject some additional processing.

Interceptors

When implementing natively with the Android SDK, most customers use interceptors to fetch an Approov token and add it to each API request’s headers, so we’ll want to fully implement this abstraction in our production module. For this simple example though, we’ll hardwire the interception in a fetchWithToken() call.

In the fetchWithToken() method, when the native fetch token call completes, if the promise is resolved, we add the token to the input request headers and make a fetch() call with the augmented input request. When completed, the fetch returns a resolved promise holding the API server’s response.

For convenience, we create an Approov object from the NativeModules.Approov object, adding a fetch() method which is actually the fetchWithToken() method, and then we export this as the Approov module.

Getting Shapes

Now we are ready to use the Approov object for authentication. We add a getShape() method inside our App which makes an Approov.fetch(request) call to authenticate and request a random shape value. Once the fetch completes, the App component state updates, triggering a render() call which causes the ShapeView to display an updated shape and status message.

A Get Shapes button is added to the button bar to request new shapes.

Everything looks good, but when we request a new shape, we see a failure with a 400 status code, suggesting there is a problem with the client request.

Failed Shapes Failure to fetch a shape

The call fails because the integrity token added by Approov is invalid. Until our example app is properly registered with the Approov service, the fetchWithToken() call will always fail the authentication check.

Command line registration tools are included in the demo download. To register the app, issue a registration request specifying the App’s IPA archive and the app registration token you saved from the demo download email. You can generate the IPA archive from the rndemo.app product inside Xcode. As a courtesy to other demo users, set your registration to expire after a few hours using the -e flag:

$ cd <<approov-demo-package>>/registration-tools/Android/Mac/
$ ./registration 
   -a <<your-rndemo.ipa>>
   -t <registration-token>
   -e 2h

Submitting data…
Success: new app signature added to database.

Once the app is registered and can be properly authenticated, pressing the Get Shapes button should return one of these shapes:

Successful Shapes Successfully fetching random shapes

Man in the Middle Attacks

The security of the communication channel is very important during API calls. If the channel is insecure, an API call could be intercepted and modified. An integrity token, although it has a short lifetime, could be observed in the insecure channel and used to make malicious API calls with impunity.

Despite using HTTPS/TLS when making API requests, an attacker who controls both the network and the mobile device can easily setup a Man in the Middle (MitM) attack to steal and quickly reuse Approov tokens before they expire.

To counter MitM attacks, mobile clients should use certificate or public key ‘pinning’ which checks that the certificate or public key presented by the back-end service is known specifically by the client app. Other certificates, though they might appear authentic, will be rejected by the client, and no API calls will be made.

Implementing pinning in React Native is a bit complicated and will be described in a separate article and integrated into this example’s code repository.

Going Further

We’ve demonstrated a native module implementation in React Native with a hardwired interceptor successfully providing app authentication and API protection.

A production quality native module implementation for React Native would generalize the interceptor functionality, add convenience configuration methods, and provide full MitM protection. For comparison, a similar Approov plugin library already exists for Cordova and Ionic hybrid apps.

All code for this example is located on github.

Category: React Native Tagged: Mobile Android API Security React Native