Shielding the Application via the OneSpan Mobile Portal

When a configuration is created using the OneSpan Mobile Portal, it is possible to shield an application. You can bind your application to App Shielding via the OneSpan Mobile Portal either manually or automated.

Manual shielding

Shielding modifies the executable of the application, which means that after shielding, the application needs to be re-signed.

This must be handled with special care so that all required parts of the application are re-signed.

To manually shield an app

The shielding section of the OneSpan Mobile Portal Home page is only enabled after a configuration has been created, the configuration options have been set, and the required certificates correctly uploaded.

1. In the Home page of the OneSpan Mobile Portal, select the project and configuration you want to use.

2. To upload the binary to be shielded, either click Select at the center of the page and browse to the file location, or add the file via drag and drop.

3. As soon as the file upload is complete, the shielding process starts.

   The binary to shield (i.e. IPA for iOS) can be signed or unsigned.

   App Shielding provides log where you can trace the shielding progress.

4. When the shielding process is completed, the OneSpan Mobile Portal displays a notification, and you can download the zip file with the shielded binary. The file time counter next to the file sets the expiry time after which the file can not be downloaded anymore.

   Shielding modifies the executable of the application, which means that after shielding, the application needs to be re-signed.

   This must be handled with special care so that all required parts of the application are re-signed.  Ensure that the correct provisioning profile is copied, and the correct entitlements are used.