--- title: Containerization of Web Browser slug: singleconnect-reference-guide-3-3-0/containerization-of-web-browser description: Learn how to record videos of HTTP sessions using containerization with this comprehensive document. Find out about the required licenses, necessary configurations, and steps for enabling containerization. Discover how to define user access to HTTP device docTags: createdAt: 2023-04-26T08:02:35.000Z --- In order to be able to record videos of the HTTP sessions, the HTTP session must be initiated with a different method than the one outlined previously. To enable the containerization feature, the corresponding licenses are required. In this section, we only address the required configurations. More details about the containerization feature can be found in our user manual How to Reach HTTP Devices Through Containers To set the resources for the containers to be created: 1. Navigate to **Administration > System Config Man**. 2. Set the **resources.of.containers** parameter with one of these values: **local, remote, **or** all.** These values define which kind of resources will be used by the container manager. ![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/VPKC-7BVQyumAH9X46VUa_image.png "Selecting Host/s for Containers") To define which user(/s) should reach HTTP devices through containers: 1. Navigate to **User Accounts > User Group Definition > Device Group Properties.** 2. Set the **accessOverContainer** property key as true. ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/5tQ5Y2RUfyqwogUxYqRMK_image.png" size="72" width="642" height="631" caption="User Group Properties" position="center" showCaption="true"} ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/Og1s_5FOVO97uk54Le2Xk_image.png" size="72" width="871" height="190" caption="Property Key" position="center" showCaption="true"} To specify which HTTP device access to use containerization: 1. Navigate to** Device Inventory > Device Properties.** 2. Set the **accessOverContainer **value as **true.** ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/q_0iCW_4xYGZ3Fnp7aWme_image.png" size="72" width="531" height="307" caption="Device Properties" position="center" showCaption="true"} ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/l3nEH0iogvQoba6m1PKT4_image.png" size="72" width="575" height="130" caption="Property Key" position="center" showCaption="true"} After saving this setting couple, some of the additional properties will be loaded automatically. Those automatically set Property Keys can be found on the below screen below. ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/YQOkYt6_MBQXBA6ToRwmj_image.png" size="72" width="633" height="419" caption="Automatically Loaded Attributes" position="center" showCaption="true"} The HTTP Proxy CA certificate and Kron extension need to be installed after reaching the container for the first time. Then the browser profile needs to be copied to the container volume to be used by newly created containers in the future. There is no need for Proxy Settings on the browser. The process is the same for AS-IS HTTP Proxy use through a native browser. To Copy the CA certificate from the PAM instance to the shared volume and complete the initial setup: 1. Open the containerized browser through the PAM Management UI or Desktop Client. ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/IGdZ4-XaIRCGJTWLik66-_image.png" size="72" width="495" height="402" caption="Through PAM Management UI" position="center" showCaption="true"} ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/a1smG6FVbDcq_qlTYE6kz_image.png" size="72" width="445" height="416" caption="Through Desktop Client App" position="center" showCaption="true"} 1. Open an SSH session to the PAM instance. Get the running container id from the session window that opened on the first step. **$ docker ps --format {{.ID}}** 2. Use the docker id to copy the CA certificate to the container **$ docker cp /u01/http-proxy/assets/ca.crt :/home/ubuntu/Desktop** The CA certificate can be found on the Desktop and it needs to be added and trusted by the browser. The same procedure needs to be followed for HTTP Proxy native web browser usage. To install the Firefox extension: 1. The same procedure should be used for native browser usage. 2. It would be useful to pin the extension onto the toolbar. ![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/1X_98ctfOo3XajvhfZQYN_image.png "Kron Extension") - Activate the extension and close the Firefox app. ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/IV1UPU7sookrgaiTkVN7q_image.png" size="50" width="281" height="162" caption="Active the Extension" position="center" showCaption="true"} To copy current settings to the shared volume: 1. It is important to close the Firefox app, otherwise, open tabs will be prompted at every single container. 2. Run the command below on the container’s terminal: **mkdir -p /shared\_volume/mozilla/firefox\_orig && cp -a \~/.mozilla/firefox/\*.default-release /shared\_volume/mozilla/firefox\_orig && cp -a \~/.mozilla/firefox/profiles.ini /shared\_volume/mozilla/firefox\_orig** ![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/0VDdbvGMeTJtyuGMCuXPG_image.png "Firefox Profile Location") This step needs to be completed only once before end users start using containers daily. From now on, that HTTP device can be reached only from the PAM Management UI and Desktop Client App by the defined individual accounts. ::Image[]{src="https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/F1crdV3fG4weNELBfqr2y_image.png" size="72" width="594" height="478" caption="Access Over Container" position="center" showCaption="true"} ![](https://api.archbee.com/api/optimize/g9cApVza9NIhSh0pjZYtA/KUi2MZiVTK1YDgEEU5dOa_image.png "HTTP Proxy Authentication Page")