Approov Quickstart: Android Java OkHttp

This quickstart is written specifically for native Android apps that are written in Java and use OkHttp for making the API calls that you wish to protect with Approov. If this is not your situation then check if there is a more relevant quickstart guide available.

This page provides all the steps for integrating Approov into your app. Additionally, a step-by-step tutorial guide using our Shapes App Example is also available.

To follow this guide you should have received an onboarding email for a trial or paid Approov account.

ADDING APPROOV SERVICE DEPENDENCY USING JITPACK

The Approov integration is available via jitpack. This allows inclusion into the project by simply specifying a dependency in the gradle files for the app.

Firstly, jitpack needs to be added to the end the repositories section in the build.gradle file at the top root level of the project:

allprojects {
    repositories {
        ...
        maven { url 'https://jitpack.io' }
    }
}

Secondly, add the dependency in your app's build.gradle:

dependencies {
	 implementation 'com.github.approov:approov-service-okhttp:3.2.3'
}

Make sure you do a Gradle sync (by selecting Sync Now in the banner at the top of the modified .gradle file) after making these changes.

This package is actually an open source wrapper layer that allows you to easily use Approov with OkHttp. This has a further dependency to the closed source Approov SDK.

ADDING APPROOV SERVICE DEPENDENCY USING MAVEN

The Maven repository is already present in the gradle.build file so the only import you need to make is the actual service layer itself:

implementation("io.approov:service.okhttp:3.2.3")

MANIFEST CHANGES

The following app permissions need to be available in the manifest to use Approov:

<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.INTERNET" />

Note that the minimum SDK version you can use with the Approov package is 21 (Android 5.0).

Please read this section of the reference documentation if targeting Android 11 (API level 30) or above.

INITIALIZING APPROOV SERVICE

In order to use the ApproovService you must initialize it when your app is created, usually in the onCreate method:

import io.approov.service.okhttp.ApproovService;

public class YourApp extends Application {
    @Override
    public void onCreate() {
        super.onCreate();
        ApproovService.initialize(getApplicationContext(), "<enter-your-config-string-here>");
    }
}

The <enter-your-config-string-here> is a custom string that configures your Approov account access. This will have been provided in your Approov onboarding email.

USING APPROOV SERVICE

⚠️ CAUTION

You MUST never reuse an OkHttpClient object but instead obtain one from the ApproovService BEFORE making a request

You can then make Approov enabled OkHttp API calls by using the OkHttpClient available from the ApproovService:

OkHttpClient client = ApproovService.getOkHttpClient();

This obtains a cached client to be used for calls that includes an interceptor that protects channel integrity (with either pinning or managed trust roots). The interceptor may also add Approov-Token or substitute app secret values, depending upon your integration choices. You should thus use this client for all API calls you may wish to protect.

You must always call this method whenever you want to make a request to ensure that you are using the most up to date client. Failure to do this will mean that the app is not able to dynamically change its pins.

Approov errors will generate an ApproovException, which is a type of IOException. This may be further specialized into an ApproovNetworkException, indicating an issue with networking that should provide an option for a user initiated retry (which must make the new request with a call to the getOkHttpClient to get the latest client).

CUSTOM OKHTTP BUILDER

By default, the method gets a default client constructed with new OkHttpClient(). However, your existing code may use a customized client with, for instance, different timeouts or other interceptors. For example, if you have existing code:

OkHttpClient client = new OkHttpClient.Builder().connectTimeout(5, TimeUnit.SECONDS).build();

Pass the modified builder to the ApproovService framework as follows:

ApproovService.setOkHttpClientBuilder(new OkHttpClient.Builder().connectTimeout(5, TimeUnit.SECONDS));

This call only needs to be made once. Subsequent calls to ApproovService.getOkHttpClient() will then always a OkHttpClient with the builder values included.

If you need multiple different builders in your application, with different configurations, then this is possible with named builders. This is an example of how to set one:

ApproovService.setOkHttpClientBuilder("short-timeout", new OkHttpClient.Builder().connectTimeout(5, TimeUnit.SECONDS));

Then in order to obtain a client using that builder use:

OkHttpClient client = ApproovService.getOkHttpClient("short-timeout");

CHECKING IT WORKS

Initially you won't have set which API domains to protect, so the interceptor will not add anything. It will have called Approov though and made contact with the Approov cloud service. You will see debug level logging from Approov saying UNKNOWN_URL.

Your Approov onboarding email should contain a link allowing you to access Live Metrics Graphs. After you've run your app with Approov integration you should be able to see the results in the live metrics within a minute or so. At this stage you could even release your app to get details of your app population and the attributes of the devices they are running upon.

NEXT STEPS

To actually protect your APIs and/or secrets there are some further steps. Approov provides two different options for protection:

• API PROTECTION: You can use this if you control the backend API(s) being protected and are able to modify them to ensure that a valid Approov token is being passed by the app. An Approov Token is short lived crytographically signed JWT proving the authenticity of the call.

• SECRETS PROTECTION: This allows app secrets, including API keys for 3rd party services, to be protected so that they no longer need to be included in the released app code. These secrets are only made available to valid apps at runtime.

Note that it is possible to use both approaches side-by-side in the same app.

See REFERENCE for a complete list of all of the ApproovService methods.