You should use this option if you wish to protect app secrets, including API keys. Rather than build secrets into an app, where they might be reverse engineered, they are only provided at runtime by Approov for apps that pass attestation. This substantially improves your protection and prevents these secrets being abused by attackers.
These additional steps require access to the Approov CLI, please follow the Installation instructions.
In order for secrets or API keys to be protected when being transmitted externally by the app, it is necessary to inform Approov about the domains on which they may be sent. Execute the following command:
approov api -add your.domain -noApproovToken
This informs Approov that it should be active for the domain, but does not need to send Approov tokens for it. Adding the domain uses Managed Trust Roots to ensure that the channel will be protected against Man-in-the-Middle (MitM) attacks.
It is assumed that you already have some client secrets and/or API keys in your app that you would like to migrate for protection by Approov. You must inform Approov what the value of each secret is as follows:
approov secstrings -addKey your-secret-name -predefinedValue your-secret-value
Note that this command requires an admin role.
These values can be changed at any time and will propagate within 5 minutes to all running instances of your apps. Since earlier released versions of the app may have already leaked your-secret-value, you may wish to refresh the secret at some later point when any older version of the app is no longer in use. You can of course do this update over-the-air using Approov without any need to modify the app.
You can define up to 16 different secret values in this way.
If the secret is presented in an API header or query parameter, and you are able to use the ApproovService networking stack, then Approov can automatically substitute the secret value at runtime. You should use this method wherever possible.
If the published code of your app currently uses your-secret-value then replace it with the value your-secret-name. This provides a placeholder value which can then be automatically substituted with the actual secret value at runtime, for validly attesting apps. The shipped app code will only contain the placeholder values.
If the secret value needs to be provided on the header your-header then it is necessary to notify the ApproovService that the header is subject to substitution. You do this by making the call once, after initialization:
http.approovAddSubstitutionHeader("your-header", "");With this in place the Approov networking interceptor should replace the your-secret-name with your-secret-value as required when the app passes attestation. Since the mapping lookup is performed on the secret name you have the flexibility of providing different secrets on different API calls, even if they are passed with the same header name.
You can see a worked example for the Shapes app.
If the secret value is provided as a parameter in a URL query string with the name your-param then it is necessary to notify Approov that the query parameter is subject to substitution. You are recommended to make this call just after Approov initialization:
http.approovAddSubstitutionQueryParam("your-param");After this the Approov networking interceptor should transform any instance of a URL such as https://your.domain/endpoint?your-param=your-secret-name into https://your.domain/endpoint?your-param=your-secret-value.
In some cases it might not be possible to automatically substitute a secret in a header or query parameter. This might be because the secret is used in other ways in your application.
In this case it is possible to make an explicit call at runtime to obtain the secret value, for apps passing attestation. Here is an example for using the required method:
http.approovFetchSecureString("your-secret-name", null)
.then(secret => {
// use secret as required, but never cache or store its value - note secret will be null if the
// provided secret name is not defined
})
.catch(error => {
if (error.type == "rejection")
// failure due to the attestation being rejected, see error.message. error.rejectionARC
// and error.rejectionReasons may be used to present information to the user (note
// error.rejectionReasons is only available if the feature is enabled, otherwise it is
// always an empty string)
else if (error.type == "network")
// failure due to a potentially temporary networking issue, allow for a user initiated retry,
// see error.message
else
// a more permanent error, see error.message
});IMPORTANT: The secrets obtained should only ever be communicated externally from the app over channels using the Approov networking stack and which have been added as protected API domains. If not then it is possible for them to be intercepted by a Man-in-the-Middle (MitM) attack.
If the app is not recognized as being valid by Approov then an exception is thrown on the network request and the API call is not completed. The secret value will never be communicated to the app in this case.
If you wish to provide more specific information about the cause of the rejection then you must use the precheck capability that can provide more detailed information in the error returned to the failure function. You should consider adding the precheck call in any network request error handling in your app, as follows:
http.get('http://ionic.io', {}, {})
.then(data => {
// successful network request
})
.catch(error => {
// error - try and determine if this is due to an Approov issue
http.approovPrecheck()
.then(() => {
// the precheck completed successfully so error seems unrelated to Approov
})
.catch(error => {
if (error.type == "rejection")
// failure due to the attestation being rejected, see error.message, error.rejectionARC and
// error.rejectionReasons may be used to present information to the user (note error.rejectionReasons
// is only available if the feature is enabled, otherwise it is always an empty string)
else if (error.type == "network")
// failure due to a potentially temporary networking issue, allow for a user initiated retry,
// see error.message
else
// a more permanent error, see error.message
})
});If the app is rejected then you may want to consider providing some feedback to the user about the issue.
If you wish to provide more direct feedback then enable the Rejection Reasons feature:
approov policy -setRejectionReasons on
Note that this command requires an admin role.
You will then be able to get information in rejectionReasons in the form of a comma separated list of device properties responsible for causing the rejection.
You should add the signing certificate used to sign apps so that Approov can recognize your app as being official.
Add the local certificate used to sign apps in Android Studio. The following assumes it is in PKCS12 format:
approov appsigncert -add ~/.android/debug.keystore -storePassword android -autoReg
See Android App Signing Certificates if your keystore format is not recognized or if you have any issues adding the certificate. This also provides information about adding certificates for when releasing to the Play Store. Note also that you need to apply specific Android Obfuscation rules when creating an app release.
These are available in your Apple development account portal. Go to the initial screen showing program resources:
Click on Certificates and you will be presented with the full list of development and distribution certificates for the account. Click on the certificate being used to sign applications from your particular Xcode installation and you will be presented with the following dialog:
Now click on the Download button and a file with a .cer extension is downloaded, e.g. development.cer. Add it to Approov with:
approov appsigncert -add development.cer -autoReg
If it is not possible to download the correct certificate from the portal then it is also possible to add app signing certificates from the app.
Apps built to run on the iOS simulator are not code signed and thus auto-registration does not work for them. In this case you can consider forcing a device ID to pass to get a valid attestation.
In order to run on a iOS device the process is a little more involved because you need to generate an IPA file. You should build the app with:
ionic cap build ios
This will launch Xcode. From there select Product -> Archive. When the archiving is complete a dialog will be shown, select Distribute App for the archive. If you just wish to register a development release then select Development in the next step which asks about distribution options. When you are ready to publish your app, you will select App Store Connect here. In the next Development distribution options step just leave the default options and click Next. You probably also wish to use the default in the Re-sign "App" step too. Finally you will come to the Review App.ipa content step and you can Export to a folder of your choice. You can then run the app on the device using:
ionic cap run ios
See Exploring Other Approov Features for information about additional Approov features you may wish to try.
You may wish to set a development key in order to force an app to be passed, if it may be resigned by a different app signing certificate to which you don't have access. Perform the call:
http.approovSetDevKey("uDW9FuLVpL1_4zo1");See using a development key to understand how to obtain the development key which is the parameter to the call.
In some cases the value to be substituted on a header may be prefixed by some fixed string. A common case is the presence of Bearer included in an authorization header to indicate the use of a bearer token. In this case you can specify a prefix as follows:
http.approovAddSubstitutionHeader("Authorization", "Bearer ");This causes the Bearer prefix to be stripped before doing the lookup for the substitution, and the Bearer prefix added to the actual secret value as part of the substitution.
In addition to secret values defined in the Approov cloud, it is also possible to get and set secure string values independently for each app instance. These are never communicated to the Approov cloud service, but are encrypted at rest using keys which can only be retrieved by passing apps. You can use this feature to protect user authorization tokens issued to individual apps or other sensitive customer data, for instance.
App instance secure strings can be set and retrived using the secret fetching code. You can define a new value for a given secret name by passing a value in the second parameter of approovFetchSecureString, rather than null. An empty string may be used to delete the secure string completely.
If you wish to reduce the latency associated with substituting the first secret, then make this call just after the Approov initialization:
http.approovPrefetch()This initiates the process of fetching the secrets in the background as soon as Approov is initialized, so that they are available immediately when subsequently needed.
You may wish to do an early check in your app to present a warning to the user if it is not going to be able to access secrets because it fails the attestation process. Here is an example of calling the appropriate method:
http.approovPrecheck()
.then(() => {
// the precheck completed okay
})
.catch(error => {
if (error.type == "rejection")
// failure due to the attestation being rejected, see error.message, error.rejectionARC and
// error.rejectionReasons may be used to present information to the user (note
// error.rejectionReasons is only available if the feature is enabled, otherwise it is always
// an empty string)
else if (error.type == "network")
// failure due to a potentially temporary networking issue, allow for a user initiated retry,
// see error.message
else
// a more permanent error, see error.message
});Note you should NEVER use this as the only form of protection in your app, this is simply to provide an early indication of failure to your users as a convenience. You must always also have secrets essential to the operation of your app, or access to backend API services, protected with Approov. This is because, although the Approov attestation itself is heavily secured, it may be possible for an attacker to bypass its result or prevent it being called at all. When the app is dependent on the secrets protected, it is not possible for them to be obtained at all without passing the attestation.