This topic explains how to configure message proxies that send and receive messages over an HTTP Proxy that routes traffic based on the “Host” header.   HTTP Forward proxies are best used with Mobile applications where the backend service endpoint is not configurable or in applications under test when there is no configuration option available to change the host and port used to connect to a backend service.

...

• Service host: [Virtualize]
• Service forward path: /path
• Mode: Secondary

Installing the Parasoft Root Certificate Authority on Mobile Emulators

Before you can use an HTTP forward proxy on a mobile emulator, the Parasoft Root Certificate Authority must be installed as a trusted certificate. If the certificate authority is not installed, the browser will not consider the connection secure and may refuse to allow the connection.

Android Emulator

iOS Emulator

Android Emulator

Anchor
Android Android

This procedure assumes that you are using Android Studio/Android Sdk and that you have created an Android Virtual Device (AVD) on a non-production build. Additionally:

• The AVD's proxy settings have been configured for Parasoft. See https://developer.android.com/studio/run/emulator-networking#proxy for more information about using the emulator with a proxy.
• The Android Sdk emulator and adb executables have been added to the $PATH variable.

Because CA certificates in Android are stored by their hashed name with the file extension .0, you will need to copy and rename the Parasoft certificate. To do that, open a command prompt and navigate to <VIRT_INSTALL_DIR>/plugins/com.parasoft.ptest.libs.web_<version>/root/lib then run the following command:

hashed_name=`openssl x509 -inform PEM -subject_hash_old -in parasoft.cer | head -1` && cp parasoft.cer $hashed_name.0

You need to place the hash.0 version of the CA certificate in the system certificate store in the Android filesystem, found at /system/etc/security/cacerts/. The /system partition is mounted as read-only by default, however, so you will first need to change permissions to it. Exactly how you do that depends on what version of the emulator you are using.

API Level 29 or higher

Starting with API Level 29, you can't mount the "/" partition with read-write permissions normally. Google has provided a workaround (see https://android.googlesource.com/platform/system/core/+/master/fs_mgr/README.overlayfs.md for more information), but some users find that this results in their emulator getting stuck in a boot loop. If that's the case, you can try the workaround detailed below:

1. Start your AVD:

   Code Block
   language text
   emulator -avd <AVD_NAME> -writable-system

   • If you're not sure of the name of your AVD, run emulator -list-avds to pull up a list of all your AVDs.

2. Restart adb as root:

   Code Block
   language text
   adb root

3. Disable secure boot verification: 

   Code Block
   language text
   adb shell avbctl disable-verification

4. Reboot the device and restart adb as root: 

   Code Block
   language text
   adb reboot adb root

5. Remount the partitions as read-write: 

   Code Block
   language text
   adb remount

   • If adb indicates that you need to reboot, run adb reboot and adb remount again.

6. Push the hash.0 version of the certificate: 

   Code Block
   language text
   adb push <PATH_TO_CERT> /system/etc/security/cacerts

7. Set certificate permissions: 

   Code Block
   language text
   adb shell chmod 664 /system/etc/security/cacerts/<NAME_OF_HASH.0_CERT>

8. Reboot the device again: 

   Code Block
   language text
   adb reboot

API Level 28 or less

1. Start your AVD:

   Code Block
   language text
   emulator -avd <AVD_NAME> -writable-system

   • If you're not sure of the name of your AVD, run emulator -list-avds to pull up a list of all your AVDs.

2. Restart adb as root:

   Code Block
   language text
   adb root

3. Remount the partitions as read-write: 

   Code Block
   language text
   adb remount

   • If adb indicates that you need to reboot, run adb reboot and adb remount again.

4. Push the hash.0 version of the certificate: 

   Code Block
   language text
   adb push <PATH_TO_CERT> /system/etc/security/cacerts

5. Set certificate permissions: 

   Code Block
   language text
   adb shell chmod 664 /system/etc/security/cacerts/<NAME_OF_HASH.0_CERT>

6. Reboot the device again: 

   Code Block
   language text
   adb reboot

iOS Emulator

Anchor
iOS iOS

1. Host the parasoft.cer file on a file server or email the parasoft.cer file to an address the iOS emulator can receive. You will find the parasoft.cer file in <VIRT_INSTALL_DIR>/plugins/com.parasoft.ptest.libs.web_<version>/root/lib.
2. Open a browser to the URL of the parasoft.cer file or open the email and follow the dialog prompts and accept the configuration profile.
3. Go to Settings > General > Device Management and select "Parasoft Root Certificate Authority." Click through the installation dialogs leaving the default settings in place.

On recent iOS versions, you also need to enable full trust for the Parasoft Root Certificate. To do so:

1. Go to Settings > General > About > Certificate Trust Settings.
2. Under “Enable full trust for root certificates”, turn on trust for the Parasoft Certificate.